Tried updating from 25295.1000. Got to 100% and GSOD with error in FLTMGR.sys. Reverted to a previous backup of the same release and it failed again with the same error.

Just got this error trying one update from 25300 to 25309, it reverted back to 25300.

Tried updating from 25295.1000. Got to 100% and GSOD with error in FLTMGR.sys. Reverted to a previous backup of the same release and it failed again with the same error. Have you tried running sfc /scannow? Have you run the Windows Update Troubleshooter? Are all your drivers up to date? Also please file this issue in the Feedback Hub. WIN+F

Thanks Sibro. It didn't show the error code when I rebooted back to 25300,, so I used CK's suggestion to use Update History. All it shows is the code 0xc19000101. I'll try some of the suggestions in that link tomorrow when I have time.

Had similar problems it finally took me 5 times to get 25309 loaded with a messed up desktop. error codes differ after each attempt were 0xc1900101, 0x80242016 and 0xc190012f. Tried "clean install", Tried emptying Software Distribution. Don't have "system Restore backup (is this still a thing), don't have extra antivirus. etc Could not get SetupDiag.exe to work, (have been unable to use this for several previous builds) followed your link to download latest version but requirements say "Only for windows 10", and it needs a .Net version older than what's current and installation of other versions is actively blocked. Can anyone advise a current surefire way to get the logs or whatever is needed to provide more concise feedback on what is actually causing my specific problems other than 0x1900101 https://aka.ms/AAjvw38

RS-Prerelease build 25309 out to Dev Channel

CrazyKats 19,585 Volunteer Moderator

Live in W.U.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

107 answers

Anonymous

2023-03-03T02:16:10+00:00

Tried updating from 25295.1000.

Got to 100% and GSOD with error in FLTMGR.sys.

Reverted to a previous backup of the same release and it failed again with the same error.
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T02:25:44+00:00

Just got this error trying one update from 25300 to 25309, it reverted back to 25300.
Was this answer helpful?

0 comments No comments
CrazyKats 19,585 Reputation points Volunteer Moderator

2023-03-03T02:46:56+00:00

Tried updating from 25295.1000.

Got to 100% and GSOD with error in FLTMGR.sys.

Reverted to a previous backup of the same release and it failed again with the same error.

Have you tried running sfc /scannow?

Have you run the Windows Update Troubleshooter?

Are all your drivers up to date?

Also please file this issue in the Feedback Hub. WIN+F
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T03:13:12+00:00

Thanks Sibro. It didn't show the error code when I rebooted back to 25300,, so I used CK's suggestion to use Update History. All it shows is the code 0xc19000101. I'll try some of the suggestions in that link tomorrow when I have time.
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T03:14:13+00:00

Had similar problems it finally took me 5 times to get 25309 loaded with a messed up desktop.

error codes differ after each attempt were 0xc1900101, 0x80242016 and 0xc190012f.

Tried "clean install", Tried emptying Software Distribution. Don't have "system Restore backup (is this still a thing), don't have extra antivirus. etc

Could not get SetupDiag.exe to work, (have been unable to use this for several previous builds) followed your link to download latest version but requirements say "Only for windows 10", and it needs a .Net version older than what's current and installation of other versions is actively blocked.

Can anyone advise a current surefire way to get the logs or whatever is needed to provide more concise feedback on what is actually causing my specific problems other than 0x1900101 https://aka.ms/AAjvw38
Was this answer helpful?

0 comments No comments