Suggestion for Pending File Rename check

[Ian Broadbent]

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 renamed at the next system reboot. This happens when Updates have installed but the system needs a reboot to finalize the installation.

I used that registry key check in my Office 2016 deployment script, it helped to avoid issues during deployment (we were uninstalling Office 2010 and 2013, then installing Office 2016).

Perhaps this registry key could be checked before the PatchCleaner analysis runs, this may help improve the accuracy of the analysis.

Regards,
Ian

[HomeDev]

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]
Sent: Friday, 6 October 2017 9:33 AM
To: [patchcleaner:discussion] general@discussion.patchcleaner.p.re.sf.net
Subject: [patchcleaner:discussion] Suggestion for Pending File Rename check

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 renamed at the next system reboot. This happens when Updates have installed but the system needs a reboot to finalize the installation.

I used that registry key check in my Office 2016 deployment script, it helped to avoid issues during deployment (we were uninstalling Office 2010 and 2013, then installing Office 2016).

Perhaps this registry key could be checked before the PatchCleaner analysis runs, this may help improve the accuracy of the analysis.

Regards,
Ian

---

Suggestion for Pending File Rename check https://sourceforge.net/p/patchcleaner/discussion/general/thread/5ba75440/?limit=25#5da9

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/patchcleaner/discussion/general/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/