Hello,
I was able to recover many GBytes with this tool on different systems, thanks for that.
now it seems to me that MS Office 2010 installations don't like to get security updates anymore.
Office 2013 and 2016 are updated as expected. A hint came from the F-Secure Softwareinstaller (helps to stay current with many apps by applying updates by group policies) which fails to install the missing updates, trying it by hand with the msi package says that the previous product is not installed.
operating systems here are Win7 x64 or Server 2008R2 with RDP. Machines out of physical reach and therefore not treated with patchcleaner are updating as expected.
I will try to reinstall the last SP, but maybe there are more dependencies than thought when deleting orphans.
some more ideas?
Thanks, Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can confirm this issue. I wrote an email already, but sadly never got a reply.
I had to completely uninstall and reinstall Office 2010 to get updates again.
Meanwhile I found the main problem: PatchCleaner detects the large file which includes the "Service Pack 2" as orphaned. If you delete or move that file Windows Update won't find any Office 2010 updates anymore! After moving that file back to the hidden directory Windows Updates finds Office 2010 updates again. But sadly, still not all updates! Some of the other "orphaned" and moved files are needed also to find all available Office 2010 updates. At last I had to move all "orphaned" files back.
It seems that it is not safe to use PatchCleaner if you are using a MSI-based Office version.
Regards,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just so you know HomeDev is a one man band so not like I have any army of
people responding to the emails that I get..
Sorry to hear it has caused issues on Office 2010? You are the only person
to have reported this to date?
I am currently running Office 2016 and have no issues with updates, and was
probably running 2013 when I first created patch cleaner, and had no issues
with these.
I have plans to release a new version with a bit more configuration to allow
you to exclude certain items from patch cleaner.
All I can say is that, PatchCleaner is offered with the warning that it may
do the wrong thing, which is why the move feature is recommended until you
are comfortable with how it works for you.
In my case I know that Adobe Acrobat does not play nice with PatchCleaner.
When I get to making a new version of PathCleaner, I will see if I can throw
up a Virtual Machine with office 2010 to see if I can reproduce.
Most Office 2013 and 2016 installations are based on Microsofts Click-To-Run technology. Therefore, they don't longer need Windows Update and the MSI/MSP files. Probably that's the reason why you don't have any issues with your Office versions.
However, installations of Office 2010 and prior mainly use Windows Update and the MSI/MSP files.
Counting Roberts first post, we are currently two persons who noticed the issue. But I think many users just won't notice that Windows Update stops updating their Office. Who regularly check the Windows Update history?
Thanks again and kind regards,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does PatchCleaner check for patch files in the registry under: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches\ ?
I found msp files under that key that were for Office 2010 (and possibly other versions of MSI-installed Office) and Silverlight that PatchCleaner found as "orphaned". (Many corporations use the MSI-installer for Office 2013 & 2016 and not the click-to-run version.) The S-1-5-18 identifier relates to the Windows local system account which is used to install patches via WSUS etc.
I have used PatchCleaner to free up files on PCs, but at next reboot Windows spends 5-10 minutes 'applying Windows updates', or similar, sorting itself out after the msi and msp have been removed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have never experienced "Applying windows updates" after running patch cleaner.
I would be interested if you are able to reproduce this every time?
I have run this hundreds of times on many different computers, and I know there are companies that have PatchCleaner running as a admin untility on entire organisations computers to automatically clean their pc's and have not had this feedback from anyone else?
I have had the odd support request in the past where PatchCleaner was being blamed for things, which after further investigation by the user led to apologies as it was a user issue.
Removing a msi or msp file from your computer should not cause any change to windows itself. The only potential issue is that next time you attempted to apply an update to that product the update may fail.
It should not cause any change that affects windows on reboot.
I suspect you had a windows update run in the background and your reboot conincedently.
Also, I would recommend to NEVER run PatchCleaner whilst windows is running a windows update as the system would be in a state of flux and it may treat recently downloaded patches as orphaned.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All -- Just found this thread, and yes patch cleaner 1420 will break Office 2010 updates. Moving the [SP2?] MSP file from the backup location into C:\WINDOWS\Installer fixed the Office update problem. It's the ~ 450 mb .msp file. Other than this, it works great!
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I was able to recover many GBytes with this tool on different systems, thanks for that.
now it seems to me that MS Office 2010 installations don't like to get security updates anymore.
Office 2013 and 2016 are updated as expected. A hint came from the F-Secure Softwareinstaller (helps to stay current with many apps by applying updates by group policies) which fails to install the missing updates, trying it by hand with the msi package says that the previous product is not installed.
operating systems here are Win7 x64 or Server 2008R2 with RDP. Machines out of physical reach and therefore not treated with patchcleaner are updating as expected.
I will try to reinstall the last SP, but maybe there are more dependencies than thought when deleting orphans.
some more ideas?
Thanks, Robert
Hello,
I can confirm this issue. I wrote an email already, but sadly never got a reply.
I had to completely uninstall and reinstall Office 2010 to get updates again.
Meanwhile I found the main problem: PatchCleaner detects the large file which includes the "Service Pack 2" as orphaned. If you delete or move that file Windows Update won't find any Office 2010 updates anymore! After moving that file back to the hidden directory Windows Updates finds Office 2010 updates again. But sadly, still not all updates! Some of the other "orphaned" and moved files are needed also to find all available Office 2010 updates. At last I had to move all "orphaned" files back.
It seems that it is not safe to use PatchCleaner if you are using a MSI-based Office version.
Regards,
Michael
Hi Michael,
Just so you know HomeDev is a one man band so not like I have any army of
people responding to the emails that I get..
Sorry to hear it has caused issues on Office 2010? You are the only person
to have reported this to date?
I am currently running Office 2016 and have no issues with updates, and was
probably running 2013 when I first created patch cleaner, and had no issues
with these.
I have plans to release a new version with a bit more configuration to allow
you to exclude certain items from patch cleaner.
All I can say is that, PatchCleaner is offered with the warning that it may
do the wrong thing, which is why the move feature is recommended until you
are comfortable with how it works for you.
In my case I know that Adobe Acrobat does not play nice with PatchCleaner.
When I get to making a new version of PathCleaner, I will see if I can throw
up a Virtual Machine with office 2010 to see if I can reproduce.
In the mean time, sorry for the inconvenience.
Regards
John
Last edit: HomeDev 2017-10-04
Hi John,
thanks for your reply and the clarification.
Most Office 2013 and 2016 installations are based on Microsofts Click-To-Run technology. Therefore, they don't longer need Windows Update and the MSI/MSP files. Probably that's the reason why you don't have any issues with your Office versions.
However, installations of Office 2010 and prior mainly use Windows Update and the MSI/MSP files.
Counting Roberts first post, we are currently two persons who noticed the issue. But I think many users just won't notice that Windows Update stops updating their Office. Who regularly check the Windows Update history?
Thanks again and kind regards,
Michael
Does PatchCleaner check for patch files in the registry under: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches\ ?
I found msp files under that key that were for Office 2010 (and possibly other versions of MSI-installed Office) and Silverlight that PatchCleaner found as "orphaned". (Many corporations use the MSI-installer for Office 2013 & 2016 and not the click-to-run version.) The S-1-5-18 identifier relates to the Windows local system account which is used to install patches via WSUS etc.
I have used PatchCleaner to free up files on PCs, but at next reboot Windows spends 5-10 minutes 'applying Windows updates', or similar, sorting itself out after the msi and msp have been removed.
Hi Ian,
I have never experienced "Applying windows updates" after running patch cleaner.
I would be interested if you are able to reproduce this every time?
I have run this hundreds of times on many different computers, and I know there are companies that have PatchCleaner running as a admin untility on entire organisations computers to automatically clean their pc's and have not had this feedback from anyone else?
I have had the odd support request in the past where PatchCleaner was being blamed for things, which after further investigation by the user led to apologies as it was a user issue.
Removing a msi or msp file from your computer should not cause any change to windows itself. The only potential issue is that next time you attempted to apply an update to that product the update may fail.
It should not cause any change that affects windows on reboot.
I suspect you had a windows update run in the background and your reboot conincedently.
Also, I would recommend to NEVER run PatchCleaner whilst windows is running a windows update as the system would be in a state of flux and it may treat recently downloaded patches as orphaned.
Cheers
All -- Just found this thread, and yes patch cleaner 1420 will break Office 2010 updates. Moving the [SP2?] MSP file from the backup location into C:\WINDOWS\Installer fixed the Office update problem. It's the ~ 450 mb .msp file. Other than this, it works great!
George