This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 77%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
After installing Windows update KB5127936, an ASUS VivoBook X515EA running Windows 11 Home stopped booting normally.
The computer displays the ASUS logo, then goes to a black screen or restarts, eventually entering Automatic Repair with an SrtTrail.txt error.
Troubleshooting performed:
Uninstalled/rolled back the latest quality update, but the issue persisted.
Attempted Startup Repair, which was unsuccessful.
Rebuilt the EFI boot files and BCD configuration without success.
The computer was operating before the update, and the failure occurred immediately afterwards. I suspect KB5127936 may have introduced a boot-related issue or triggered corruption that was not reversed when the update was uninstalled.
Has anyone else experienced boot failures after installing KB5127936? Is Microsoft aware of any compatibility issues, and is there a recommended repair procedure that does not require reinstalling Windows? I had to completely wipe the PC and start fresh.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 20%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
I have the same issue on a Dell XPS desktop. I was able to recover using a previous recovery point. I delayed updates for a few days while I looked for cause.... but no definitive issue found. I let the update go thru today.... same issue.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hello,
Welcome to the Microsoft Windows Community.
Good evening, @Brian . Let’s try a repair using Windows RE:
1. Connect the charger, hold down the Shift key, and restart the computer three consecutive times when the Asus logo appears.
2. Once you reach the repair screen, click on "Advanced options" -> "Reset this PC" -> "Get started" -> "Keep my files."
Please let us know the outcome.
Hi Dio,
This will not work, after resetting, and doing the update, it will fail again on the PC.
Regards,
Brian
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 43%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi Dio,
I am experiencing a nearly identical issue with KB5127936 on a Dell XPS 8960 running Windows 11 25H2. After the installation, the computer would no longer boot. There was no error message; the system immediately attempted an automatic repair, followed by a restart - which simply led back into another automatic repair loop...
Using a recovery medium from my backup software, I discovered that the update had scrambled my drive designations. My system contains three SSDs and one HDD; following the update, my C: drive had been reassigned as the E: drive. I was able to correct this using DISKPART, but the computer still failed to boot, continuing to cycle endlessly through automatic repairs. I suspect the update altered or corrupted the boot partition. I managed to resolve the situation by restoring a backup of the entire volume containing both the C: drive and the boot partition. Afterward, I paused my backups - though this is hardly a proper solution.
Best regards,
Hans
Hi,
I’m glad that’s resolved, Brian.
Please consider rating my support by clicking "yes" or "no" under "Was this response helpful?"
Hi, @BNPM617 . Access your device's BIOS and go to "Advanced Options" -> Boot => Enable the "Windows Boot Manager" option -> Save your changes by pressing F4 or F10, and let me know if the problem has been resolved.
Hi Dio,
The Windows Boot Manager was already enabled. Do you have any further suggestions?
Best regards,
Hans
I can only say that restoring a version that does not contain that update has resolved the issue. I have turned off updates and will not get anymore updates until this issue is resolved.
Regards,
Brian
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 64%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
I had similar issue - PC could not boot. Got error 0xc0000225. No recovery options worked for me. Luckily had a Macrium backup of entire disk.
When restored backup image, KB5127936 was again scheduled to reinstall. Could not prevent this even with Updates Paused and Get latest updates turned off. Had do do a lot of hacking to get rid of pending updates. There needs to be a better way of doing this.
I have stopped updates for a month and hope KB127936 issue resolved by then.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
