Win 10 LTSC KB5082200 BSOD CRITICAL PROCESS FAILED after slimming with NTLite

J

johnny7pop

New Member
Messages
24
Reaction score
3
Hello
I've just recently made an image with the latest update for win 10 "kb5082200-x64" but after using the preset that I've already had made and tested I get BSOD CRITICAL PROCESS FAILED.
I wish I could find the root cause to it but can't find any logs with any crash information, after a day trying different settings I've retested the iso with the 10th March 2026 update kb5078885-x64 and using exactly the same preset and windows works with no problems. Normally I would skip that update but it does patch up 2 zero days so I would prefer to have it.
Has anyone maybe encountered this issue or maybe have a solution?
 

Attachments

johnny7pop said:
Hello
I've just recently made an image with the latest update for win 10 "kb5082200-x64" but after using the preset that I've already had made and tested I get BSOD CRITICAL PROCESS FAILED.
I wish I could find the root cause to it but can't find any logs with any crash information, after a day trying different settings I've retested the iso with the 10th March 2026 update kb5078885-x64 and using exactly the same preset and windows works with no problems. Normally I would skip that update but it does patch up 2 zero days so I would prefer to have it.
Has anyone maybe encountered this issue or maybe have a solution?
Click to expand...

I can confirm the same BSOD and I think I figured out what's causing it.

It seems to be linked to the removal of "Telemetry Client" under Windows Error Reporting API. Once I stopped removing it for new images, the BSOD problems stopped.

Try creating another image without removing "Telemetry Client" and the image should work again.

Hopefully nuhi can investigate this and issue a fix.
 
Last edited:
Thanks ! I will try it shortly and report back.

I can confirm that this solution of keeping "Telemetry Client" unfortunately works, I mean unfortunately as I hate to have to keep it, seems like microslop wants to make telemetry mandatory, ah well luckily I'm slowly transitioning to fedora and bazzite for gaming, need windows just as a backup after all this years if I can't do something on linux I can return to win10 for something.
Thanks for the help! Much appreciated!
Hopefully nuhi will find a workaround or something.
 
Last edited:
johnny7pop said:
Thanks ! I will try it shortly and report back.

I can confirm that this solution of keeping "Telemetry Client" unfortunately works, I mean unfortunately as I hate to have to keep it, seems like microslop wants to make telemetry mandatory, ah well luckily I'm slowly transitioning to fedora and bazzite for gaming, need windows just as a backup after all this years if I can't do something on linux I can return to win10 for something.
Thanks for the help! Much appreciated!
Hopefully nuhi will find a workaround or something.
Click to expand...

Even though it's still installed, you can still use NTLite to disable the telemetry service.

It looks like MS updated some telemetry files with the latest update. If you try to remove it, it essentially bricks the OS after you reboot. I have hopes it will get resolved in a future update.
 
Meedas said:
Even though it's still installed, you can still use NTLite to disable the telemetry service.

It looks like MS updated some telemetry files with the latest update. If you try to remove it, it essentially bricks the OS after you reboot. I have hopes it will get resolved in a future update.
Click to expand...
Thanks I've checked and it works fine with service disabled, but from the past I remember that some services would re-enable sometimes, therefore I always prefered removal instead, but this will suffice for now. Thanks again!
 
I have 2 the same coinciding with kb5082200 and same boot error CRITICAL PROCESS FAILED, haven't tried keeping keeping telemetry but that would something on both images that was removed. And no issues like that on either image before. My initial suspicion was the boot.wim got stepped on twice somehow but no, that wasn't it.
 
Meedas said:
I can confirm the same BSOD and I think I figured out what's causing it.

It seems to be linked to the removal of "Telemetry Client" under Windows Error Reporting API. Once I stopped removing it for new images, the BSOD problems stopped.

Try creating another image without removing "Telemetry Client" and the image should work again.

Hopefully @nuhi can investigate this and issue a fix.
Click to expand...
Many thanks Meedas,
i've mounted in Virtualbox a image of LTSC IoT 2021 with a telemetry client, and seems that all works fine.
Before i try without telemetry and a BSOD appears during a installation.
I hope this component gets marked as a must-have for NtLite, at least for LTSC builds.
The LTSC IoT version is the one that will retain updates until 2032, and I hope it's monitored by the NTLite project manager, the great Nuhi.
It would be helpful if someone could release a preset for this version that would ensure the update without having to refresh the system every month.
 
Just tested a non-LTSC version of Windows 10 and the same error occurs. So this issue is not limited to LTSC, it appears to affect regular Windows 10 as well.
 
essentially - the way components are marked, whether they are "safe" for windows install, oobe, etc is a lie at the moment. including components reported AGES ago (like EFS) are still not marked as essential for successful installation
 
You must log in or register to reply here.
Back
Top