Michael Posted October 18, 2021 Posted October 18, 2021 Afternoon all, I use an XML file for file associations which has worked perfectly (for literally years), via GPO only to notice Google Chrome has now started to become the PDF default, despite my file specifying Adobe Reader DC as the default. I've told users who have raised the issue to change the default manually (which works), but not sure what I can do centrally to resolve this? Anyone else experienced this? Everything else is applying correctly.
Michael Posted October 18, 2021 Author Posted October 18, 2021 Think I've resolved this, but no idea why it's become a problem now - Computer Config > Policies > Admin Templates > Google > Google Chrome - Always open PDF files externally - Enabled 1
smurfomatic Posted October 18, 2021 Posted October 18, 2021 Some of our staff noticed this recently (well, they said "PDFs now appear as internet files", which took a bit of working out) and I can only assume it's an update to Chrome that has hijacked the file association - thanks for pointing out the solution 1
andyk1975 Posted October 19, 2021 Posted October 19, 2021 We have exactely the same issue in school. GP applying a 'File Association XML' file always set Adobe Reader as the defualt App for PDF files. Again, as you have said, this has now reverted to opening using Google Chrome. Very frustrating for staff. I too found the GP setting you mentioned but ours was already enabled and so, for us, I don't think that is our solution. The only thing I can see that has changed is our machine our updating now to 2004 build of windows 10. However, it seems to be quite randon, so we are still looking at GP not applying.
Cw2k Posted October 19, 2021 Posted October 19, 2021 Has you acrobat reader updated itself to 64bit as the 64bit uses different naming to the 32bit 1
andyk1975 Posted October 19, 2021 Posted October 19, 2021 Thanks, I'll look into this. It's a possibilitiy.
Michael Posted October 19, 2021 Author Posted October 19, 2021 Just an update on this, the above GPO does not work as expected, so I'm back to square one. The only working method is manually (as per my screenshot)!
Cw2k Posted October 19, 2021 Posted October 19, 2021 Thanks, I'll look into this. It's a possibilitiy. 64bit reader is based on the Pro installer acropro.msi rather than acroread.msi has some change he to the ProgID table so looks like it is using Acrobat.Document.DC rather than AcroExch.Document.DC, not had a chance to test in our config yet
Michael Posted October 19, 2021 Author Posted October 19, 2021 What's frustrating is if I manually set Google Chrome as the PDF viewer and reboot the machine, the GPO is applying correctly re-applying Adobe Reader as the default (in my user context). So the question is, given it's a machine GPO (the XML file), it's not quite clear why it's working for some and not all users as before suddenly?
Michael Posted October 20, 2021 Author Posted October 20, 2021 I still don't have a solution to this, other than manually change (as above). The issue appears randomly and I've read articles as old as 2017 where this has become an issue with Google Chrome. You can't set file associations in a user context via GPO or a regedit, as it generates a random hash in the registry when initiated by a user. As above I'm already deploying an XML file in a computer context which is working in my tests. Beginning to wonder whether this is something user initialised, as I couldn't re-create the issue no matter what I tried. Anyone else had any joy?
jthompson Posted October 20, 2021 Posted October 20, 2021 I remember giving up on PDF file association in Win10. MS decided to make PDF a special case, because security, such that it was harder to wrestle default handler status away from browsers without the user doing it for themself. Can't remember the specifics, but that was the gist of it.
Michael Posted October 21, 2021 Author Posted October 21, 2021 I remember giving up on PDF file association in Win10. MS decided to make PDF a special case, because security, such that it was harder to wrestle default handler status away from browsers without the user doing it for themself. Can't remember the specifics, but that was the gist of it. I'm kind of getting to this stage too, but would prefer if it was streamlined. Would be nice if a Google GPO would allow nomination of a third party app, such as Adobe.
Olliesaurus Posted October 24, 2021 Posted October 24, 2021 I found that the ProgramID had magically changed with an update, had to change the ProgramID in my XML file for it to work. I can’t remember what it changed from and to though. I’d recommend logging in as local admin, setting the file association though the GUI then running the PS script to export it to an XML and find out what the new ProgramID is then change your existing XML. Probably teaching to suck eggs but because the ID is different it defaults back to browser.
Michael Posted October 24, 2021 Author Posted October 24, 2021 I found that the ProgramID had magically changed with an update, had to change the ProgramID in my XML file for it to work. I can’t remember what it changed from and to though. I’d recommend logging in as local admin, setting the file association though the GUI then running the PS script to export it to an XML and find out what the new ProgramID is then change your existing XML. Probably teaching to suck eggs but because the ID is different it defaults back to browser. Would you mind posting your export so we can compare?
Olliesaurus Posted October 25, 2021 Posted October 25, 2021 Would you mind posting your export so we can compare? Yeah sure, I’ll be honest, it’s a mess so I’ll pull the tidy bit if that’s OK! Will set myself a reminder to post it tomorrow.
timbo343 Posted October 28, 2021 Posted October 28, 2021 So this prompted me to look at ours because a couple of users were having the same issue. Here is what i found: Changed to: Not sure if it will work - will know on Monday i guess.
Michael Posted November 1, 2021 Author Posted November 1, 2021 This link details the correct parameters, so according to Adobe what I have set is correct. I think someone needs to nudge Adobe that it's not working!
timbo343 Posted November 1, 2021 Posted November 1, 2021 This link details the correct parameters, so according to Adobe what I have set is correct. I think someone needs to nudge Adobe that it's not working! I found my solution didn't actually work so reverted back to the old way.
Michael Posted November 2, 2021 Author Posted November 2, 2021 Thanks for the feedback. Anyone any joy with this?
howartp Posted November 2, 2021 Posted November 2, 2021 https://winaero.com/how-to-export-and-import-file-associations-in-windows-10/ I used the DISM command on my own PC, having set the association to Reader DC manually, then copied the XML line out of it into our central copy.
Michael Posted November 3, 2021 Author Posted November 3, 2021 I've looked a bit more into this as follows - Adobe Acrobat Reader DC (64-bit), build no. 2021.007.20099, running the export command reads: Adobe Acrobat Reader DC (32-bit), build no. 2021.007.20099, running the export command reads: Question is, can you enter both entries in a single XML file for multiple environments? I'm 99% sure only Adobe Acrobat Reader DC (32-bit) is being used in environments I manage.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now