0x800f0986 windows server 2019 — Ваш верный помощник с OS Windows

Microsoft Support & Malware Removal
Windows Update

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[SOLVED] Windows Server 2019 Update Error 0x800f0986

Thread starter
Thread starter

ANorton
Start date
Start date

Mar 22, 2024

Joined: Mar 22, 2024

Posts: 12

I have been getting this error on different servers with different roles but wanted to start with a single server. I have run updates, manual updates stopped/started services and renamed folders. SFCSCAN now fails, DISM fails.

The CBS log is 150MB right now so not sure I can upload it.

2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:10, Info 2024-03-22 07:55:12, Error 2024-03-22 07:55:12, Error [gle=0x80004005]
2024-03-22 07:55:12, Error 2024-03-22 07:55:12, Error 2024-03-22 07:55:12, Info Expected: {l:32 Actual: {l:32 b:9023f8aa 2024-03-22 07:55:18, Error 2024-03-22 07:55:18, Error [gle=0xd0000056]
2024-03-22 07:55:18, Error [gle=0x80004005]
2024-03-22 07:55:18, Error 2024-03-22 07:55:19, Error 2024-03-22 07:55:19, Error 2024-03-22 07:55:19, Info 2024-03-22 07:55:19, Error 2024-03-22 07:55:19, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Error 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:20, Info 2024-03-22 07:55:53, Info 2024-03-22 07:55:53, Info 2024-03-22 07:55:53, Info 2024-03-22 07:55:53, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:55, Info 2024-03-22 07:55:58, Error 2024-03-22 07:55:58, Info 2024-03-22 07:55:58, Info 2024-03-22 07:55:58, Info 2024-03-22 07:58:49, Info 2024-03-22 07:58:49, Info 2024-03-22 07:58:49, Info 2024-03-22 08:01:01, Info 2024-03-22 08:01:01, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240322113223.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321215117.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321193300.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321182646.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321063145.log to WER report.
CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CSI 0000000f (F) Hydration failed with original error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: 1 , IntegrityState Valid: true , RetrievedChecksum: 1616011332 , ComputedChecksum: 1616011332[gle=0x80004005]
CSI 00000010@2024/3/22:11:55:12.644 (F) onecore\base\wcp\deltahydrator\deltahydrator.cpp(64): Error 800f0986 [Warning,Facility=15 (0x000f),Code=2438 (0x0986)] originated in function DeltaHydrator::`anonymous-namespace’::GetPsfxSpecificError expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x986))) )
CSI 00000011 (F) Hydration failed for component Microsoft-Windows-UtilMan, version 10.0.17763.1697, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file Utilman.exe with NTSTATUS -2146498170[gle=0x80004005]
CSI 00000012@2024/3/22:11:55:12.644 (F) Attempting to mark store corrupt with category [l:18 ml:19]’CorruptPayloadFile'[gle=0x80004005]
CSI 00000013 Hashes for file member [l:11]’Utilman.exe’ do not match.
ml:4096 b:006eab15d43639b420ac7380a923230cb47d96f35a0b0377538ff49725efc23e}.
eda4a1da45ac477a81b5bbe4128e413f19a0abfa3715465ad66ed5cd}.
CSI 00000014 (F) STATUS_DELETE_PENDING #5247519# from Windows::Rtl::SystemImplementation:irectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= («null»)}, da = (DELETE|SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES), oa = @0xc83290ca18->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[129]’\SystemRoot\WinSxS\Temp\InFlight\17a07cc14f7cda0137530000e423641f\02f230c34f7cda01c8530000e423641f_windows.ui.blockedshutdown.pri’; aOBJ_CASE_INSENSITIVE)}, iosb = @[gle=0xd0000056]
CSI 0xc83290ca80, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
CSI 00000015@2024/3/22:11:55:18.941 (F) onecore\base\wcp\sil\ntsystem.cpp(2987): Error STATUS_DELETE_PENDING originated in function Windows::Rtl::SystemImplementation:irectFileSystemProvider::SysCreateFile expression: (null)
CSI 00000016 (F) STATUS_DELETE_PENDING #5247515# from Windows::Rtl::SystemImplementation::CDirectory:eleteRecursively(…)[gle=0xd0000056]
CSI 00000017 (F) 800f0986 [Error,Facility=(000f),Code=2438 (0x0986)] #5161142# from Windows::COM::CComponentStore::InternalTransact(…)[gle=0x800f0986]
CSI 00000018 (F) 800f0986 [Error,Facility=(000f),Code=2438 (0x0986)] #5138056# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 1, a = @0x1d7ebee3070, fn = @0x1d7ebee3870, fp = @0x1d7ebee4070, disp = 0, op = 0)[gle=0x800f0986]
CBS Failed to add to transaction package: Package_9614_for_KB5035849~31bf3856ad364e35~amd64~~10.0.1.19 [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Failed to stage execution package: Package_9614_for_KB5035849~31bf3856ad364e35~amd64~~10.0.1.19 [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS CommitPackagesState: Started persisting state of packages
CBS CommitPackagesState: Completed persisting state of packages
CSI 00000019@2024/3/22:11:55:20.769 CSI Transaction @0x1d7ead61880 destroyed
CBS Perf: Stage chain complete.
CBS Failed to stage execution chain. [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Failed to process single phase execution. [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19, status: 0x800f0986, failure source: Stage, start state: Resolved, target state: Installed, client id: UpdateAgentLCU
CBS Not able to query DisableWerReporting flag. Assuming not set… [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240322113223.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321215117.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321193300.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321182646.log to WER report.
CBS Added C:\Windows\Logs\CBS\CbsPersist_20240321063145.log to WER report.
CBS Not able to add %windir%\winsxs\poqexec.log to WER report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS Reboot mark cleared
CBS Winlogon: Simplifying Winlogon CreateSession notifications
CBS Winlogon: Deregistering for CreateSession notifications
CBS FinalCommitPackagesState: Started persisting state of packages
CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19, current: Resolved, pending: Default, start: Resolved, applicable: Installed, target: Installed, limit: Installed, status: 0x0, failure source: Stage, reboot required: False, client id: UpdateAgentLCU, initiated offline: False, execution sequence: 77, first merged sequence: 77, reboot reason: REBOOT_NOT_REQUIRED, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Security Update, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0
CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19, current: Resolved, original: Resolved, target: Installed, status: 0x800f0986, failure source: Stage, failure details: «(null)», client id: UpdateAgentLCU, initiated offline: False, execution sequence: 77, first merged sequence: 77, pending decision: InteractiveInstallFailed, primitive execution context: Interactive
CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
CBS FinalCommitPackagesState: Completed persisting state of packages
CBS Enabling LKG boot option
CBS Exec: Download qualification evaluation, business scenario: Automatic Corruption Repair
CBS Exec: Network Cost API is not available on this SKU, continue.
CBS Exec: Network detected as Unknown, continue
CBS Exec: Addsource called, Session: 31095885_796367432, Client: UpdateAgentLCU, from GPO: Yes, Path: \\?\C:\Windows\CbsTemp\31095885_796367432\Windows10.0-KB5035849-x64.cab\
CBS Exec: Installation failed and store corruption mark found, attempt auto corruption repair.
CBS Engine: Add thread to the execution waiting queue: 7944
CBS Exec: Processing complete. Session: 31095885_796367432, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19, Identifier: KB5035849 [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Engine: Try to wake up thread for execution: 7944
CBS Engine: Thread ready for execution: 7944
CBS Exec: Session processing started. Client: Auto, Session(UpdateAgentLCU Store Corruption Detect/Repair): 31095885_796367432
CBS Reboot mark set
CBS Winlogon: Registering for CreateSession notifications
CBS Failed to perform operation. [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Session: 31095885_796367432 finalized. Reboot required: no [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Failed finalizing session [HRESULT = 0x800f0986 — PSFX_E_APPLY_FORWARD_DELTA_FAILED]
CBS Failed to call Process on TiWorker session [HRESULT = 0x800f0986]
CBS Repr: CBS Store check completes
CSI 0000001a StoreCorruptionRepair transaction begun. WcpVersion: [l:38]’10.0.17763.5568 (WinBuild.160101.0800)’.
CSI 0000001b@2024/3/22:11:58:49.202 Starting corruption detection (InnerFlags=10)
CBS WU creates the package, AppID:wusa, UpdateID:{065BAE89-0767-4C9F-A5C4-7A59E1CB79AA}, revision: 501
CBS Session: 31095888_2618978372 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null

Thank you for any help and assistance you can provide.

Joined: Mar 22, 2024

Posts: 12

Here is a result from just DISM.

Attachments

CBS.log

Joined: Mar 22, 2024

Posts: 12

Here is the entire log directory in zip format.

Thanks!

Attachments

CBS.zip

Joined: Mar 22, 2024

Posts: 12

Hope everyone had a great weekend. Just checking in.

Joined: Mar 22, 2024

Posts: 12

I see the same issue with a couple people in other posts with the same files. Can I use those fixes to try and fix the issue I am seeing?

Thanks
Aaron

Maxstar

Moderator, Windows Update Expert, Security Analyst

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

Attachments

SFCFix.zip

Joined: Mar 22, 2024

Posts: 12

Running DISM /online /cleanup-image /RestoreHealth now but here is the log as requested,

Thanks for the help!

Attachments

SFCFix.txt

Joined: Mar 22, 2024

Posts: 12

DISM came back successful, running the windows update now.

Thank You!

Maxstar

Moderator, Windows Update Expert, Security Analyst

Great, let me know the result. If it fails attach a new copy of the CBS logs.

Joined: Mar 22, 2024

Posts: 12

Quick update, the update is stuck at 75% currently, Will keep an eye on it.

Maxstar

Moderator, Windows Update Expert, Security Analyst

This is something you see quite often, as long as no error message appears it should be fine…

Joined: Mar 22, 2024

Posts: 12

We have success! this can be marked as solved. Thank you!

Maxstar

Moderator, Windows Update Expert, Security Analyst

Hi,

You’re welcome. Glad to hear this server is up-to-date now, so I will mark this thread as solved…

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Microsoft Support & Malware Removal
Windows Update

Источник

When you’re faced with the frustrating “Error 0x800f0986” while trying to install the Cumulative Update for Windows Server 2019, don’t despair. Here are two effective solutions to get your server up-to-date,

How to fix Windows Server 2019 Updates Failed with Error 0x800f0986

Solution 1: Execute DISM with RestoreHealth

Open an administrative Command Prompt.
Type the following command and press Enter:
```
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:"*HealthyMachine*\C$\Windows" /LimitAccess
```
(Replace “HealthyMachine” with the name of a server that has successfully installed all patches, including the current month’s updates.)
Reboot your server.
Attempt to install the problematic update again. It should now install successfully.

Solution 2: Reset Windows Update Service

Open an administrative Command Prompt.

Enter the following commands one by one, pressing Enter after each:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Close the Command Prompt.
Check if Windows Updates are now functioning properly.

By following these straightforward steps, you can overcome the update roadblock and ensure your Windows Server 2019 is secure and up-to-date. Don’t let update errors hinder your server’s performance – take control and apply these solutions today.

Источник

Устанавливала январское кумулятивное обновление KB5022286 на сервера Windows Server 2019 Datacener и почти на все сервера оно встало без проблем (в том числе и на Core).
Но на двух Core-серверах оно отказалось устанавливаться. И через WSUS и вручную выдает ошибку 0x800f0986
Что характерно, оба этих сервера — контроллеры домена DC01 и DC02, хотя не понимаю как это может быть связано.

Ни одно из решений найденных в гугле не помогло:

1. Остановка службы (net stop wuauserv) и переименование/удаление содержимого папки SoftwareDistribution
2. Сброс настроек Windows Update вручную
3. Сброс настроек Windows Update с помощью скрипта ResetWUEng
4. Скачивание кумулятива и попытка установить его вручную тоже выпадает в такую же ошибку
5. Запуск SFC /scannow ничего не находит
6. Repair-WindowsImage -Online –ScanHealth говорит что требуется восстановление, но dism /Online /Cleanup-Image /RestoreHealth на полпути сбрасывается так как не видит путь к файлам.

Причем другие обновления устанавливаются и вручную и через WSUS, ошибку выдает только кумулятивное.
Кто-нибудь сталкивался с подобным?

Последнее редактирование: 24.01.2023

Хм, а перезагрузка?

Хм, а перезагрузка?

И не раз. Все тщетно.

Проблема у меня оказывается была в том, что я отключил Защитник Windows и SuperFetch чтоб не грузили систему. Включив их обновление прошло успешно!

А такое пробовали ?

Команда
sc query WinDefend — выдает что защитник windows включен и работает….

Код:

SERVICE_NAME: WinDefend
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

Последнее редактирование: 26.01.2023

Команда
sc query WinDefend — выдает что защитник windows включен и работает….

SERVICE_NAME: WinDefend
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

По идее ошибка говорит о повреждении системных файлов, а если явно отсюда поставить, тоже эффекта не будет ?

Последнее редактирование модератором: 25.01.2023

По идее ошибка говорит о повреждении системных файлов, а если явно отсюда поставить, тоже эффекта не будет ?

Да, именно отсюда я скачивала кумулятивное обновление и пробовала установить вручную — ошибка такая же.

Повреждение системный файлов определенно есть, о чем говорит статус Repairable:

Код:

PS C:\Users\admin> Repair-WindowsImage -Online -ScanHealth

Path             :
Online           : False
ImageHealthState : Repairable
RestartNeeded    : False

Только вот Repair-WindowsImage -Online -RestoreHealth не исправляет файлы — говорит что не найден путь к файлам. И если пытаюсь указать путь на скачанный с сайта Microsoft образ с Windows Server 2019, тоже самое. Видимо версия отличается.

Последнее редактирование: 26.01.2023

Источник

The update error 0x800F0986 may occur if the essential system files are corrupt. Moreover, corrupt Windows update components may also cause the issue at hand. The user encounters the issue while updating the OS of his system. The error 0x800F0986 is reported to occur with many feature and quality updates. Usually, the following type of message is shown:

Installation Failure: Windows failed to install the following update with error 0x800F0986

Windows Failed to Install the Update Error 0x800F0986

Solution 1: Run the Windows Update Troubleshooter

You may fail to update the Windows of your system if the update modules of the OS are stuck in operation. In this case, running the Windows built-in Update Troubleshooter may solve the problem.

Press the Windows key and open Settings.
Now, select Update & Security, and in the left pane of the update window, navigate to the Troubleshoot tab.

Картинка с сайта: appuals.com

Open Update & Security
Then, in the right pane, click on the Additional Troubleshooters and select the Windows Update to expand it (in Get Up and Running section).

Картинка с сайта: appuals.com

Open Additional Troubleshooters
Now click on the Run the Troubleshooter button and let it complete its process.
Then after implementing the suggestions by the troubleshooter, check if the updates are working fine.

Solution 2: Manually Install the Windows Updates

If the automatic Windows updates are failing to install, then using the standalone installer of the update may solve the problem.

Launch a web browser and navigate to the Windows 10 page of the Microsoft website.
Now, under the latest update (e.g., October 2020 Update), click on the Update Now button.

Картинка с сайта: appuals.com

Click on the Update Now in the Windows 10 Download Page
Then download the offline installer and once the download is complete, launch it as administrator.
Now follow the prompts to complete the update process and then reboot your PC.
Upon reboot, check if the Windows is clear of the update error.

If you are encountering the issue with a particular update (e.g., KB4598242), then you may use the following steps (you can find the latest KB on the Microsoft website):

Launch a web browser and navigate to the Windows Updates Catalog
Now, in the search box, enter the problematic KB (e.g., KB4598242) and press the Enter key.
Then, in the results, download the KB as per your OS and system.

Картинка с сайта: appuals.com

Download the Offline Installer of the KB4598242 Update
Now launch the downloaded update installer as administrator and follow the prompts to complete the setup process.
Then reboot your PC and check if the updates can be installed without any issue.

Solution 3: Use SFC and DISM Scans

You may encounter the Windows update error 0x800F0986 if the essential operating system files are corrupt. In this context, performing the SFC and DISM scans may clear the files’ corruption and thus solve the problem.

Perform an SFC scan of your system (make sure to try when you can spare your system for some time as the scan may take some time to complete) and then check if the update issue is resolved.
If not, then try DISM to repair Windows in an elevated Command Prompt but during this process, make sure to execute the following command:
```
DISM.exe /Online /Cleanup-image /Restorehealth
```
Картинка с сайта: appuals.com

Use the DISM Command to RestoreHealth
Once the DISM process is complete, check if the system is clear of the error 0x800F0986.

Solution 4: Reset the Windows Update Components

The issue may arise if any of the essential Windows Update Components are corrupt or stuck in the operation. In this case, resetting the Windows Update Components may solve the problem. But before proceeding, make sure to create a system restore point.

Press the Windows key and search for: Command Prompt. Then, in the results, right-click on the result of the Command Prompt, and in the mini-menu, choose Run as Administrator.
Now execute the following cmdlets (do not forget to press the Enter key after each command):
```
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
```
Картинка с сайта: appuals.com

Stop the Services Related To Update & Rename the Software Distribution and Catroot2 Folders
Then close the Command Prompt and check if the update error 0x800F0986 is resolved.

If not, then check if using the WuReset.bat file (pre-written commands to reset the Windows Update modules) resolves the issue. Make sure to launch the WuReset.bat file as administrator.

Solution 5: Perform an in-place Upgrade

If none of the solutions has worked for you, then we are left with no other option but to perform an in-place upgrade. But before proceeding, it will be good to create a system restore point and backup the essential data in the system drive. Also, make sure to remove any 3^rd party security product (at your own risk), so that the upgrade process can function without any interruption. Moreover, the secure boot may hinder the upgrade process, so make sure to disable it in the system’s BIOS. Additionally, during the process, whenever asked to, make sure to select Keep Windows Settings, Personal Files, and Apps. Last but not least, make sure your system drive has enough free space available (for 32-bit: 20GB and 64-bit: 32 GB) to complete the upgrade process.

Launch a web browser and navigate to the Windows 10 ISO download
Now scroll down and then click on the Download Tool Now (under Create Windows 10 Installation Media).

Картинка с сайта: appuals.com

Download Media Creation Tool Now
Once the download is complete, launch the setup file as administrator and follow the prompts to complete the process.

Картинка с сайта: appuals.com

Launch the Setup in Windows 10 ISO Folder as Administrator
Then reboot your PC and check if the updates issue is resolved.

If the upgrade process fails, then try the same through a Windows 10 bootable USB stick. If the issue is not resolved after the in-place upgrade, then you may perform a clean installation of Windows 10.

Kevin Arrows

Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Источник

0x800f0986 — ошибка, возникающая в Центре обновления Windows 10 во время загрузки и установки кумулятивных апдейтов для ОС. Крайне серьезная проблема, потому как пользователь теряет доступ к новым разработкам Майкрософт, однако ее относительно просто решить, воспользовавшись давно известными фиксами. В сегодняшней статье мы посмотрим с вами на эти фиксы.

Как исправить ошибку обновления 0x800f0986

Проверка службы Центра обновления

Нажмите клавиши WINDOWS+R, чтобы вызвать окошко «Выполнить».
Вставьте в доступную строчку «services.msc» (без кавычек, разумеется) и нажмите ENTER.
Опуститесь вниз списка, найдите «Центр обновления Windows» и дважды кликните на эту службу ЛКМ.
В ниспадающем меню типа запуска выберите опцию «Автоматически».
Нажмите «Запустить», «Применить» и «OK».

Запуск средства устранения неполадок

Кликните ПКМ на Пуск в углу экрана и выберите «Параметры».
Найдите в списке раздел «Обновление и безопасность» и перейдите в него.
Далее перейдите в подраздел (или вкладку) «Устранение неполадок».
Чуть ниже в окне вы увидите пункт «Дополнительные средства устранения неполадок» — кликните на него.
Выберите «Центр обновления Windows» (один из первых в списке) и нажмите на кнопку «Запустить средство устранения неполадок».
Следуйте инструкциям на экране, чтобы устранить потенциальные неполадки в Центре обновления.
Перезагрузите ПК.

Удаление содержимого папки SoftwareDistribution

Кликните на службу «Центр обновления Windows» ПКМ и выберите «Остановить».
Откройте Проводник и перейдите по пути:
- C:/Windows/SoftwareDistribution/Download
Оказавшись в папке «Download», нажмите комбинацию CTRL+A, затем — SHIFT+DELETE.
Перезагрузите ПК.

Сброс Центра обновления

Нажмите ПКМ на меню Пуск и выберите «Командная строка (администратор).
Выполните в консоли следующий ряд команд:
- net stop bits
- net stop wuauserv
- net stop cryptsvc
- Del «%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat»
- Ren %Systemroot%\SoftwareDistribution\DataStore DataStore.bak
- Ren %Systemroot%\SoftwareDistribution\Download Download.bak
- Ren %Systemroot%\System32\catroot2 catroot2.bak
- sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
- sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
- cd /d %windir%\system32
- regsvr32.exe atl.dll
- regsvr32.exe urlmon.dll
- regsvr32.exe mshtml.dll
- regsvr32.exe shdocvw.dll
- regsvr32.exe browseui.dll
- regsvr32.exe jscript.dll
- regsvr32.exe vbscript.dll
- regsvr32.exe scrrun.dll
- regsvr32.exe msxml.dll
- regsvr32.exe msxml3.dll
- regsvr32.exe msxml6.dll
- regsvr32.exe actxprxy.dll
- regsvr32.exe softpub.dll
- regsvr32.exe wintrust.dll
- regsvr32.exe dssenh.dll
- regsvr32.exe rsaenh.dll
- regsvr32.exe gpkcsp.dll
- regsvr32.exe sccbase.dll
- regsvr32.exe slbcsp.dll
- regsvr32.exe cryptdlg.dll
- regsvr32.exe oleaut32.dll
- regsvr32.exe ole32.dll
- regsvr32.exe shell32.dll
- regsvr32.exe initpki.dll
- regsvr32.exe wuapi.dll
- regsvr32.exe wuaueng.dll
- regsvr32.exe wuaueng1.dll
- regsvr32.exe wucltui.dll
- regsvr32.exe wups.dll
- regsvr32.exe wups2.dll
- regsvr32.exe wuweb.dll
- regsvr32.exe qmgr.dll
- regsvr32.exe qmgrprxy.dll
- regsvr32.exe wucltux.dll
- regsvr32.exe muweb.dll
- regsvr32.exe wuwebv.dll
- netsh winsock reset
- net start bits
- net start wuauserv
- net start cryptsvc
Закройте Командную строку и перезагрузите ПК.

Заметка: как альтернатива, можете воспользоваться особой утилитой Мануэля Гиля, которую можно скачать на официальном сайте разработчика. Установите утилиту на системный раздел диска и запустите с правами админ-аккаунта — это обязательно! Появится окошко Командной строки — выберите нужный язык и следуйте дальнейшим инструкциям.

Установка проблемного обновления вручную

Если никакие из вышеуказанных методов не помогли вам избавиться от ошибки 0x800f0986, то мы рекомендуем всецело обойти ее, установив проблемное обновление вручную через каталог Центра обновления Майкрософт. Главное — найти подходящую для своей ОС версию обновления, и запустить установщик от имени администратора, чтобы избежать потенциальный проблем.

Хочется верить, что хоть какой-то из методов помог вам избавиться от ошибки 0x800f0986.

Источник