My install green screen at 92%, system_service_exception.
Error in event log is : 0xC1900101
Feedback Hub : https://aka.ms/AAe2pev
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
My install green screen at 92%, system_service_exception.
Error in event log is : 0xC1900101
Feedback Hub : https://aka.ms/AAe2pev
Same issue. Thanks for the post / info.
Same here. Clicking on Status brings up the list of processes but not the User.
WU also rolled back an Intel Display driver the other day.
WU does the same to me too with every clean install, despite disabling WU driver updates via Group Policy before going online. In the case of sound and wi-fi drivers, the installation routine is responsible not WU, the changes do not show in WU history.
This was unrelated to a clean install and also happened to Hawkeyes.
JMO, I think that Intel released a driver that was causing a problem
and then rolled it back. The newer driver was dated 9/21/21 and it rolled
back to one dated 9/18/21.
My PC was having an issue and it hasn't happened since it rolled back.
Understood, I was just sharing my experience with something similar.
Rolling back a faulty driver is good, WU installing an undesired one is not 😉
WU also rolled back an Intel Display driver the other day.
WU does the same to me too with every clean install, despite disabling WU driver updates via Group Policy before going online. In the case of sound and wi-fi drivers, the installation routine is responsible not WU, the changes do not show in WU history.
This was unrelated to a clean install and also happened to Hawkeyes.
JMO, I think that Intel released a driver that was causing a problem
and then rolled it back. The newer driver was dated 9/21/21 and it rolled
back to one dated 9/18/21.
My PC was having an issue and it hasn't happened since it rolled back.