How to fix 0x139 error after windows update

Question

How to fix 0x139 error after windows update

Rein Süld 0

Starting from 2026 June Windows update always stuck with 0x139 error. Automatic repair is unable to repair. Only manual restore point selection will help. I disabled the Windows updates but Windows overwrites periodically direct prohibition and updates Windows anyhow ending with same error. Multiple times tried dism /online /cleanup-image /restorehealth and sfc /SCANNOW but without any success.

0 comments

1 answer

Your answer

Answer 1

David-M 127.7K Independent Advisor

Hi. I'm David, and I'm happy to help you.

When this error occurs repeatedly after a Windows update, the cause is almost always an incompatibility with a third-party driver or software.

Did you try starting Windows in Safe Mode? If so, what exactly happened?

Also, please see if you have minidump files.

These files are in C:\Windows\Minidump.

(If you don't have a Minidump folder, check if it is in the plural Minidumps.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

Looking forward to your reply.

Rein Süld 0 Reputation points

2026-09-08T14:13:33.6033333+00:00

Yes, tried all safe options. Exact same result - 0x139. Already installed Windbg but minidump folder consist only 3 files from much earlier - spring 2026. Also no full dump file under Windows folder. Boot log option has not been tried. When updated to 25H2, it's succeeded only when disabling all non-MS services, but there was no 0x139 error.
David-M 127.7K Reputation points Independent Advisor

2026-09-08T16:08:27.36+00:00
Thanks for the details.

Just to clarify on "safe options": if you were referring to the general recovery tools in the Windows Recovery Environment (like Startup Repair), those usually fail on this type of error. But if you meant actual Safe Mode, a 0x139 crash can still happen there if a bad third-party driver is set to load early at boot.

So, since the crash happens so early in the boot sequence, Windows never gets the chance to write a new minidump file, which explains why your folder only shows those older files from spring.

The fact that disabling non-Microsoft services worked for you during the 25H2 upgrade is a significant clue. It confirms that a third-party background service or kernel-level driver is interfering with the Windows Update process.

I suggest doing the following:

Perform a Clean Boot as instructed below:

Press "Windows + R", type msconfig, and hit "Enter";

Go to the "Services" tab, check "Hide all Microsoft services" (make sure not to skip this step), and click "Disable all";

Open Task Manager, go to the "Startup apps" tab, and disable all startup items.

I suggest you also remove kernel-level software: temporarily uninstall any third-party antivirus, anti-cheat software, or motherboard utilities (like Armoury Crate or MSI Center). These are the most common culprits for these crashes during updates.

Then restart (not shutdown) your PC into this clean state and try running Windows Update again.

Please let me know how it goes.

Feel free to ask any questions you may have.
Rein Süld 0 Reputation points

2026-09-08T16:45:06.8233333+00:00

I mean Windows RE safe options. For whatever reason there are no easy way to even get to RE. F8-F12 keys don't work, 3 cycles of power button pressing end always with automatic repair and only when automatic repair fails three times, RE will be available.

I will try tomorrow Clean Boot. It will take some time because I must uninstall Armoury Crate, ASUS DriveHub, ASUS AI Suite, Intel Driver And Support Assistant at first.

But many thanks for the ideas to test! Let's hope I don't have to do this with every new Windows update.
David-M 127.7K Reputation points Independent Advisor

2026-09-08T16:55:32.32+00:00

Glad to help.

If you have any questions, don't hesitate to ask.