Unable to install Security Monthly Quality Rollups for Windows 7 or update to Win 10

jselig · Jan 9, 2020

Hi,
I was asked to look at a Win 7 SP1 PC that errors out trying to update to Windows 10. I looked at Windows update and saw the following message:

Windows 10 couldn't be installed. Errors found: 8007001F-20006 Windows Updated encountered an unknown error.

I looked at the Windows update history, and see that for approx the last year the Security Monthly Quality Rollups for Windows 7 were also failing. All other updates were successful, just these Security Monthly Quality rollups were failing. So I figure I should forget about getting the update to Win 10 for the time being, and get the Win 7 update errors working first, which hopefully will clear the path for the Win 10 update.

The most recent Security Monthly Quality update that fails is KB4530734, fails with with error code 800F0900.

I noticed that there was no antivirus software running on it. They thought they had Windows Defender running. If I tried to start Windows Defender, it would not start. I was able to install Avast and ran a full scan, and it found nothing. I installed Malwarebytes Anti-Malware and ran a full scan, and it found a handful of what looked like minor "PUP's" which it successfully removed. I also had run the Windows Update Troubleshooter and that did not make any difference.

After doing the above items, here is a summary of some other items I ran with results:

cleanmgr /sageset:1
cleanmfg /sagerun:1

dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489
.............................
Completed running scanhealth, check logs at %windir%\logs\CBS\Checksur.log

The operation completed successfully.

sfc /scannow
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

Here is a CBS.zip file:
CBS.zip

I'm almost at the point of just re-installing windows but if you have any other suggestions I'd appreciate it.
Thanks,
Jim

Sysnative Windows Update · Jan 9, 2020

Hello and welcome!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, run System Update Readiness Tool again and attach CheckSUR.log.

jselig · Jan 9, 2020

Hi,
Here is the SFCFix txt file contents:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-09 19:23:59.297
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\cindy\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-nwifi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6e0ae8581c7910f9
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_40a72e2477e646bb
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394.inf_loc
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394ohci.sys.mui
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f
Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Servicing\Packages

Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-nwifi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6e0ae8581c7910f9\nwifi.sys.mui to C:\Windows\WinSxS\amd64_microsoft-windows-nwifi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6e0ae8581c7910f9\nwifi.sys.mui.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_40a72e2477e646bb\ntfs.sys.mui to C:\Windows\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_40a72e2477e646bb\ntfs.sys.mui.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394.inf_loc to C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394.inf_loc.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394ohci.sys.mui to C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394ohci.sys.mui.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\ohci1394.sys.mui to C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\ohci1394.sys.mui.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_580_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_580_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_580_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_580_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_581_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_581_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_581_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_581_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_582_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_582_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_582_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_582_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_583_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_583_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_583_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_583_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_629_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_629_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.cat.
Successfully copied file C:\Users\cindy\AppData\Local\niemiro\Archive\Packages\Package_629_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_629_for_KB4338818~31bf3856ad364e35~amd64~~6.1.1.8.mum.

Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-nwifi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6e0ae8581c7910f9
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-nwifi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6e0ae8581c7910f9
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_40a72e2477e646bb
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-ntfs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_40a72e2477e646bb
Successfully restored ownership for C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394.inf_loc
Successfully restored permissions on C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394.inf_loc
Successfully restored ownership for C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394ohci.sys.mui
Successfully restored permissions on C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f\1394ohci.sys.mui
Successfully restored ownership for C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f
Successfully restored permissions on C:\Windows\WinSxS\amd64_1394.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_beafdf583b909e3f
Successfully restored ownership for C:\Windows\Temp\CheckSur\Servicing\Packages
Successfully restored permissions on C:\Windows\Temp\CheckSur\Servicing\Packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2020-01-09 19:24:01.060
Script hash: ubz3Iie4omId4wWpFJ7EM1kxGozsfmH/XeAnqSsvxYQ=
----------------------EOF-----------------------

I then tried to run the system update readiness tool - what I downloaded is "Windows6.1-KB947821-v34-x86.msu" but when I tried to install it, I got the following response:

This update is not applicable to your computer

Is this what you were asking for?

Sysnative Windows Update · Jan 9, 2020

Hi!

You need to run the 64 bit version of the tool as you have 64 bit Windows.

jselig · Jan 9, 2020

Sorry about that, now here's the CheckSUR.log file attached...

Sysnative Windows Update · Jan 9, 2020

Looks okay. Please do the following:

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

jselig · Jan 9, 2020

Here is the cbs.txt file...

Sysnative Windows Update · Jan 9, 2020

Please run it once again.

jselig · Jan 9, 2020

Here it is again..

Sysnative Windows Update · Jan 9, 2020

Great! Please do the following:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

jselig · Jan 9, 2020

The FRST and Addition.txt files are attached.

(Minor note, fyi... I've been getting email notifications with each of your replies and then I go back to the browser to respond. This most recent reply had different email contents - instead of the seven steps shown in this thread, the email had the contents below. I followed the steps above):

______________________

Great! Please do the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Sysnative Windows Update · Jan 9, 2020

I have mistakenly copy pasted the wrong instructions and edited them immediately. My apologies.

You have attached CBS.log instead of FRST.

jselig · Jan 9, 2020

Sorry about that - thought I sorted by date and just picked the top two files without checking it... here's the correct files.

Sysnative Windows Update · Jan 9, 2020

Thank you.

I would advise you to fully remove Avast! from Safe Mode using its removal tool: https://files.avast.com/iavs9x/avastclear.exe

jselig · Jan 9, 2020

OK, will do this. When I first looked at this, Avast wasn't installed, but I added it to do a virus scan since there was no other anti-virus software running. However right now I am remotely accessing the computer with the issue - I am at home and it is in an office. I'll lose access when it is in safe mode so I'll have to go there to do this, and won't be until tomorrow. After this is removed, what should the next step be? Thanks for all of your help...

Sysnative Windows Update · Jan 9, 2020

Then you can retry upgrading to Windows 10. As a side quest, I would like to see fresh FRST logs, although, based on what I'm seeing, I think the upgrade should go in now after removing Avast.

jselig · Jan 16, 2020

Here is a final follow-up... I went into the office to bring the computer home just to make things easier. It was still powered up so I shut it down. As it was shutting down I just happened to notice a message that Windows had installed some updates. that looked hopeful and so I booted it backup and looked at the update history - I saw that the latest Security Monthly Quality Rollup had successfully installed! I went ahead and removed Avast anyway, then ran the Windows 10 update and it upgraded with no problems. Thanks again!

Sysnative Windows Update · Jan 23, 2020

Great!

Unable to install Security Monthly Quality Rollups for Windows 7 or update to Win 10

Contributor

Inactive

Attachments

Contributor

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Inactive

Contributor

Inactive