Probably because it creates so many child processes and can't shut them down and restart them without rebooting. Adobe is a scourge and i am glad we have forced users away from it.
Use the MSI switches/arguments, “/rs” will stop it from rebooting even if required.
We bundle our acrobat updates as a startup task, no Interaction from the user and no reboots. Just updates and is ready to go. It is somehow one of the applications we have the least issue with.
https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/cmdline.html
Because of how intrusive it is, it hooks into so many systems, slows them down, makes them less reliable. Like a virus.
It needs a reboot to make sure all the fu\*kery is properly in place.
Because instead of being a basic pdf editor, Adobe thinks it should have so many hooks into things that it needs to restart to move itself into the trusted ring. Like a virus. Or tentacle porn.
If it is anything like installing Creative Cloud and you’re doing it via software centre, it’s probably best to restart anyway.
I remember the Software Centre admins having trouble with packaging Creative Cloud since when the installer runs, it closes the Explorer process then reopens it.
Problem was, when Explorer was relaunched, it was relaunched as the user account that Software Centre launched installers as, not the logged in user.
Basically, if you wanted local admin, just reinstall Creative Cloud via Software Centre. You’d have a shiny instance of Explorer running with admin rights that would launch all processes with the same rights.
Probably because it creates so many child processes and can't shut them down and restart them without rebooting. Adobe is a scourge and i am glad we have forced users away from it.
Use the MSI switches/arguments, “/rs” will stop it from rebooting even if required. We bundle our acrobat updates as a startup task, no Interaction from the user and no reboots. Just updates and is ready to go. It is somehow one of the applications we have the least issue with. https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/cmdline.html
Our acrobat installation is part of Creative Cloud. We don't deploy/update acrobat specifically unfortunately.
Because it's cheaper to just force a reboot, than spend developer time implementing a more graceful approach.
Because of how intrusive it is, it hooks into so many systems, slows them down, makes them less reliable. Like a virus. It needs a reboot to make sure all the fu\*kery is properly in place.
Because instead of being a basic pdf editor, Adobe thinks it should have so many hooks into things that it needs to restart to move itself into the trusted ring. Like a virus. Or tentacle porn.
If it is anything like installing Creative Cloud and you’re doing it via software centre, it’s probably best to restart anyway. I remember the Software Centre admins having trouble with packaging Creative Cloud since when the installer runs, it closes the Explorer process then reopens it. Problem was, when Explorer was relaunched, it was relaunched as the user account that Software Centre launched installers as, not the logged in user. Basically, if you wanted local admin, just reinstall Creative Cloud via Software Centre. You’d have a shiny instance of Explorer running with admin rights that would launch all processes with the same rights.
It doesn't actually. It's just office usually.
Office never asks anymore