Activity for PatchCleaner
-
FocusedWolf modified a comment on discussion General Discussion
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. Also attached is a script i made after trying to fix the original script.
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. Also attached is a script i made after trying to fix the original script.
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. Also attached is a script i made after trying to fix the original script.
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. Also attached is a script i made after trying to fix the original script.
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. EDIT: I'll be honest here, i don't think anyone should use even my version of...
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. EDIT: I'll be honest here, i don't think anyone should use even my version of...
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes. EDIT: I'll be honest here, i don't think anyone should use even my version of...
-
I realise this is 2 years after you posted that, but you should know that batch script you linked has some MAJOR issues. I sent a comment to the creator of that script with the fixes. Luckily his script doesn't delete anything by default, and also seems to be bugged to the point of thinking all files in the installer folder are not orphaned. Attached to this message is my reply to him in case he never applies the fixes.
-
Yaskar modified a comment on discussion General Discussion
Hi, i'm using PatchCleaner to automate the clearing of the Windows Installer folder on our Windows 10 machines. I'm using it with the /d switch but cannot get it to output the results to a log file. I've tried various re-direction streams and combinations but it never outputs anything to the file. For example: patchcleaner /d > test.log The results is always presented on the screen output and the test.log is always empty. I think this is also causing an additional problem, when I remotely deploy...
-
Hi, i'm using PatchCleaner to automate the clearing of the Windows Installer folder on our Windows 10 machines. I'm using it with the /d switch but cannot get it to output the results to a log file. I've tried various re-direction streams and combinations but it never outputs anything to the file. For example: patchcleaner /d > test.log The results is always presented on the screen output and the test.log is always empty. ![]https://i.stack.imgur.com/9mngR.png) I think this is also causing an additional...
-
matt wilkie posted a comment on discussion General Discussion
Ok, so I've run Patch Cleaner and moved the files identified as orphans somewhere else. What it is the most efficient way to test that these moved files actually are safe to delete?
-
George Allen posted a comment on discussion General Discussion
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
-
HomeDev posted a comment on discussion General Discussion
The license can be viewed by running the installer, about step 2 or 3 of the installation wizard. You can Ctrl-A, Ctr-C Ctrl-V if you wish to capture it. You can read the license without having to install the product, just click cancel on that step.
-
teknowledgist posted a comment on discussion General Discussion
I understand. I was asking more to spur a posting of the license than for the code to be released.
-
Hi, The product is not 100% Open source, purely from the fact that I have a donate link within the product which would be the first thing someone would change if it was open source. HomeDev obtains a few dollars from people who the product has helped. So it is really donate-ware. It is a click-wrapped license, and the product is offered 100% free. The license that appears in the installer, is based upon the MIT license. Essentially the software is offered 100 for free but with no warranty that the...
-
Thanks for this handy utility. Most things on SourceForge are open source licenses. Is PatchCleaner being offered as OSS? Could you identify the license? Is the code available? Thanks.
-
Thanks Ian, I am working on an update to PatchCleaner, (in fact I have been doing that for a while now) I will add this to my development backlog. I think the use of the registry to read this data will allow me to by default exclude by product. As the product in the registry lists all of its patches (whether they are current or orphaned), I will be able to exclude each patch. So you may be able to tick, Silverlight and have that excluded from the clean up. Thanks John From: Ian Broadbent [mailto:ibroadbent@users.sf.net]...
-
Ian Broadbent posted a comment on discussion General Discussion
Following on from a warning you had in another post regarding Windows Updates running, one way to help prevent possible issues with PatchCleaner when Windows Updates are running or pending is to check for Pending File Renames. I have used the following line in batch scripts before: reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations If the key “PendingFileRenameOperations” is present, that means there is one (or more) files scheduled to be...
-
Thanks for the explanation about how the cleanup works (i.e. the Product key, I'm understanding more of it now. I ran the VBS script you mentioned; on one PC that has 475 msi and msp files, the script listed 88 files to keep, but only 54 were unique after I noticed some filenames were duplicated. PatchCleaner reported 173 files in use and 336 files orphaned. So looks like there is some difference between the VB Script method and PatchCleaner's. (I feel more confident in PatchCleaner given that it...
-
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...
-
Hi Ian, Yes, PatchCleaner is not fool proof. I created it originally for my own use and personally have only had issues with Adobe Reader. As you can see on this discussion board, someone has identified potential issues with Office 2010 updates, and one particular update for Silverlight seemed to have issues, although I have not experienced these myself. The product is clear that it is not 100% perfect and to use at your own risk, hence the provision of the move feature, which I recommend as the...
-
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...
-
I did more testing, I found a batch script here https://ourrick.wordpress.com/2015/04/04/find-orphaned-installer-files-in-cwindowsinstaller-folder/ which also does a detection for orphaned msi files by checking the ."HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches" key. On a Windows 7 x64 PC with 492 msi and msp files in the C:\Windows\Installer directory, I ran the script and it found 492 files, but all of them had entries in the registry. On the same PC, PatchCleaner...
-
I did more testing, I found a batch script here https://ourrick.wordpress.com/2015/04/04/find-orphaned-installer-files-in-cwindowsinstaller-folder/ which also does a detection for orphaned msi files by checking the ."HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches" key. On a Windows 7 x64 PC with 492 msi and msp files in the C:\Windows\Installer directory, I ran the script and it found 492 files, but all of them had entries in the registry. On the same PC, PatchCleaner...
-
Thanks for the PatchCleaner tool, I’ve used it a few times on Windows 7 64-bit PCs and been able to clean up several GBs. But I have noticed that after running PatchCleaner, at the next reboot, the PC spends 5-10 minutes with “applying windows updates..” or similar even though no updates have been installed recently. It seems Windows has detected some changes and needs to sort itself out. I had a look at some of the files that PatchCleaner detected as orphans and found an msp file that was a patch...
-
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...
-
Thanks for the PatchCleaner tool, I’ve used it a few times on Windows 7 64-bit PCs and been able to clean up several GBs. But I have noticed that after running PatchCleaner, at the next reboot, the PC spends 5-10 minutes with “applying windows updates..” or similar even though no updates have been installed recently. It seems Windows has detected some changes and needs to sort itself out. I had a look at some of the files that PatchCleaner detected as orphans and found an msp file that was a patch...
-
APMichael posted a comment on discussion General Discussion
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...
-
Hi Michael, Sorry for not getting back to you but I have been a bit busy building a house, and looking for a new Job, so a few things on my plate to worry about and PatchCleaner is a bit down the order on my prority list. 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...
-
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...
-
Robert Glöckner posted a comment on discussion General Discussion
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...
-
PatchCleaner released /PatchCleaner/v1.4.2.0/PatchCleaner_1.4.2.0.exe
-
-
1