Обновление для windows 10 version 1607 для систем на базе процессоров x64 kb4049411

I’m unable to update from Windows 10 Pro 1607 to 1903 — the auto update feature has been failing for months now. It usually fails and returns the message «Something went wrong — error code 0x8007007e»

I have of course tried to fix the problem myself, but unfortunately nothing I’ve tried has worked. The error code that I’m returned is apparently not uncommon, and I’ve tried to follow various suggested fixes over the past few months, but to no avail.

Steps I’ve tried before running Windows update:

— Disabling anti-virus

— Running SFC /scannow
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.

— Performing a «clean boot» through msconfig

— Control Panel -> System and Security -> Fix Problems with Windows Update — Ran the trouble shooter and fixed problems (Windows Update still failed after the troubleshooter fixed all problems successfully)

— Downloaded and ran the Windows Update troubleshooter (Windows update still failed)

— Downloaded and ran the Reset Windows Update wureset_x64 (Windows update still failed)

— Tried to upgrade to Microsoft .NET Framework 4.7 (update failed)

— Downloaded and ran the Microsoft .NET Framework Reapair Tool (still failed in updates)

— Deleted the folder «C:\Windows\SoftwareDistribution» and ran Windows Update again (it still failed)

-I’ve tried to download specific update stacks
KB4520724
2019-11 Servicing Stack Update for Windows 10 Version 1607 for x64-based Systems (KB4520724)
windows10.0-kb4520724-x64_97604f0b532d6da814b4120fc43b2d9f6fd0b356.msu

I end up getting «This update is not applicable to your computer»

==============

I think that covers most of what I’ve tried — KB4049411 and KB4033631 keep installing repeatedly successfully then 1903 Fails. I really don’t wanna have to wipe everything clean and reset my PC to its factory settings.

Despite being far from an expert, I’ve managed to sort out every PC issue I’ve ever had — this windows update problem has me totally stumped though. Nothing has been successful. I’m not IT savvy enough to be able to pinpoint what’s causing update to fail.

I’ve attached my zipped CBS logs — if anyone could help me get round this problem. PLEASE!!!

Error: 0x800f081f

The source files could not be found.
Use the «Source» option to specify the location of the files that are required to restore the feature.

SFCFix
Stage 1 of 6 failed on server
SFCFix Has Crashed
Something has gone horribly wrong and SFCFix has crashed.

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.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. 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, please run DISM again and attach CBS.log.

Thank you.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-07 08:17:07.592
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\Ruben\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browserbroker.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgfw.efi
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgr.efi

Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browserbroker.dll to C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browserbroker.dll.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browser_broker.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browser_broker.exe.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced\bootim.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced\bootim.exe.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced\bootux.dll to C:\WINDOWS\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced\bootux.dll.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\boot.stl to C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\boot.stl.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgfw.efi to C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgfw.efi.
Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgr.efi to C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgr.efi.

Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browserbroker.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1\browserbroker.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.14393.0_none_97d156cc64ee22e1
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-bootux.deployment_31bf3856ad364e35_10.0.14393.0_none_6b85b847e6f3bced
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgfw.efi
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgfw.efi
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgr.efi
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_10.0.14393.0_none_b4f55452b3127f7f\bootmgr.efi
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2019-12-07 08:17:12.254
Script hash: WzTngsUGzcV6J0ffmoXjsPGWJcNBGbsrN1cMD/tfg8o=
----------------------EOF-----------------------

CBS Log ZIP file attached

SFC Scan

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 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»

4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them.

CBS Log
CBS.log

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.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. 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.

SFC Scan

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 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»

4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-07 10:23:24.033
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\Ruben\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-shell-sounds_31bf3856ad364e35_10.0.14393.0_none_4486e7adcc3c3b8e\Windows Startup.wav

Successfully copied file C:\Users\Ruben\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-shell-sounds_31bf3856ad364e35_10.0.14393.0_none_4486e7adcc3c3b8e\Windows Startup.wav to C:\WINDOWS\WinSxS\amd64_microsoft-windows-shell-sounds_31bf3856ad364e35_10.0.14393.0_none_4486e7adcc3c3b8e\Windows Startup.wav.

Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-shell-sounds_31bf3856ad364e35_10.0.14393.0_none_4486e7adcc3c3b8e\Windows Startup.wav
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-shell-sounds_31bf3856ad364e35_10.0.14393.0_none_4486e7adcc3c3b8e\Windows Startup.wav
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2019-12-07 10:23:25.088
Script hash: 15AhmPlHXc1qIMarRvVEj0GzOdCGFXkH51Gvb36hV6Y=
----------------------EOF-----------------------

SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

CBS LOG
CBS.log

Thanks.

I am still having the same updates install. Then it said…

Feature update to Windows 10, version 1803.

So I let that install…

The computer prepares, downloads, then asks to reset….

Once reset the install begins but stops after a minute and the screen says «restoring previous version of windows»

Still the same fail as before.

Then when you go back to check for updates it is preparing to install 1903

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.

McAfee WebAdvisor
uTorrent

Afterwards, run the following fix, please:

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.