Appreciate all the feedback in this thread. Will add some comments for folks who are hitting issues. C1900101 is quite possibly my least favorite bucket of bug. It's driver-related and it quite frequently temporary. Install will fail once with that error and then immediately succeed on retry, with no changes in between. It's frustrating to say the least! As mentioned (by fg I believe), the "extended code" is important when seeing this error. If you hit it, please include the full error code, such as: 0xC1900101-0x2001 On to the FLTMGR.sys issue. This was something we saw internally before release, but it was a VERY small number of devices. Didn't have a reason to believe it would be widespread, but it's obvious folks are hitting it. We do have an active but on it and it's being investigated. There's a second bug in this space that we believe is driving a second issue as well. (One bug causing two separate issues/outcomes.) Actively digging in, that's for sure! For the folks who hit the "file missing" errors, please do file feedback. There aren't any known publishing issues, so if it's true that a file is missing off the download server, we'll need to know which one so we can trace why it didn't land correctly. Thanks as always for the feedback and for the details of what you're hitting. We're always working to improve and your feedback helps us get there!

That's a "file not found" error. I wonder what it's looking for?

Thank you for that. I did a clean install not too long ago, since so many are having trouble, i think i'll just wait for the next build. MS has a problem here and they'll find it and either post a fix or fix it for next time. Regards, Jim

I too am stuck. the setupdiag tool finds nothing. I got to 99%, bugchecked, too fast to see what it said. Next reboot but doesn't even try to reinstall. after first reboot. If i blow off the software download directory it will try again, but it just repeats. 99% and rollback. Jim 25300 is an .ISO so you could replace your build with a clean build and try the update from that? Davy.

I too am stuck. the setupdiag tool finds nothing. I got to 99%, bugchecked, too fast to see what it said. Next reboot but doesn't even try to reinstall. after first reboot. If i blow off the software download directory it will try again, but it just repeats. 99% and rollback. Jim

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-03T17:30:27+00:00

Appreciate all the feedback in this thread. Will add some comments for folks who are hitting issues.

C1900101 is quite possibly my least favorite bucket of bug. It's driver-related and it quite frequently temporary. Install will fail once with that error and then immediately succeed on retry, with no changes in between. It's frustrating to say the least! As mentioned (by fg I believe), the "extended code" is important when seeing this error. If you hit it, please include the full error code, such as: 0xC1900101-0x2001

On to the FLTMGR.sys issue. This was something we saw internally before release, but it was a VERY small number of devices. Didn't have a reason to believe it would be widespread, but it's obvious folks are hitting it. We do have an active but on it and it's being investigated. There's a second bug in this space that we believe is driving a second issue as well. (One bug causing two separate issues/outcomes.) Actively digging in, that's for sure!

For the folks who hit the "file missing" errors, please do file feedback. There aren't any known publishing issues, so if it's true that a file is missing off the download server, we'll need to know which one so we can trace why it didn't land correctly.

Thanks as always for the feedback and for the details of what you're hitting. We're always working to improve and your feedback helps us get there!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-03-03T17:20:38+00:00

That's a "file not found" error. I wonder what it's looking for?
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T14:40:51+00:00

Thank you for that. I did a clean install not too long ago, since so many are having trouble, i think i'll just wait for the next build. MS has a problem here and they'll find it and either post a fix or fix it for next time.

Regards,

Jim
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T14:03:54+00:00

I too am stuck. the setupdiag tool finds nothing. I got to 99%, bugchecked, too fast to see what it said. Next reboot but doesn't even try to reinstall. after first reboot. If i blow off the software download directory it will try again, but it just repeats. 99% and rollback.

Jim

25300 is an .ISO so you could replace your build with a clean build and try the update from that?

Davy.
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-03T13:38:35+00:00

I too am stuck. the setupdiag tool finds nothing. I got to 99%, bugchecked, too fast to see what it said. Next reboot but doesn't even try to reinstall. after first reboot. If i blow off the software download directory it will try again, but it just repeats. 99% and rollback.

Jim
Was this answer helpful?

0 comments No comments