As a hardcore packager I only add one global exclusion..
Just add c:\program files.
Then If users can save files to d: or even e: I also add then as an global exclusion.
When users save files on the network I do not use the global exclusions because they are excluded by default.
When you insatll SWV or SVS there are also two Global exclusions mentioned. These can be selected and just leave them.

As you see I never use exclusions for extensions.

Hope this helps you.

ExcludeGen isn't very smart, it grabs every file association in a layer when 90%+ of them are read or print only and not a type of file that can be written to-- the condition that allows for something to get captured into a layer.  For you example, Acrobat Reader, there's not reason to exclude anything because reader doesn't save files -- unless it's a PDF marked as revisable (so you can mark comments, like you can with Work Documents, for future revisions) and not a lot of people use that feature.

By default, unless you tell SVS/SWV not to, the user's Desktop and Documents folder is excluded which is where a lot of people tend to save stuff.  If you know people where you work tend to save where ever then you'll want to exclude a specific file extension--or use a Data Layer-- but that's the only reason people tend to use file type excludes.

You should alway's train your users to not save data on the local C disk.
I alway's tell my users what ever is on C belongs to me. I delete it if i wish.
Data on c is never in a backup. If something happens you just loose it. So start early. Make sure users do not save on C.
Educate them to save on the network drive. Then you never have to think about exclusions.

or you can use data layers so you don't have to train, because we know people never do what their told.