Fix result of Farbar Recovery Scan Tool (x64) Version: 07-05-2017
Ran by Terry (07-05-2017 20:25:40) Run:9
Running from C:\Users\Terry\Documents\Downloads\frst64
Loaded Profiles: Terry (Available Profiles: Terry & Nina & UpdatusUser)
Boot Mode: Normal
==============================================
Remove Update Manually 1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter wusa /uninstall /KB:2492386
4. Let me know if it says it was successful or if there are any errors.
Can you please do the following again? Get the capture near the fail point. It's important that the capture is running during the fail.
Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the upgrade just like you have in the past.
3. Stop Process Monitor as soon as the upgrade fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
It doesn't appear that the process monitor log file contains the entries I need. Are you sure it was capturing at the time the error came up. It looks like process monitor was started too late.
Remove Update Manually 1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter wusa /uninstall /KB:982018
4. Let me know if it says it was successful or if there are any errors.
No problem. So what's going on with these updates, we seemed to have gotten past the reboot phase before and then things regressed, was there something you found seriously wrong that we had to back track?