Guide: Optimized Image

I will leave Nuhi to troubleshoot this for now, but my gut says this is probably just a case of corruption. It takes many forms, it could be virus/malware, bad tweaks, corrupted Windows install, antivirus/firewall software, etcetera. Whenever I see permissions errors on these forums it's almost always related to that type of stuff. Corruption begets corruption.

What I would do in your scenario to rule out tons of variables all at once is to:
1. Use the PowerRun tool and run NTLite with it, then try to integrate that registry file and see if it works.
2. Do a default (no tweaks) reformat and installation of Windows, then disable Defender and integrate that registry file.

One or both of those methods should work, unless there is actually a bug in NTLite. But, since Nuhi says it works on his end, it's probably something on your computer causing the conflict. I'm not in a place where I can test this myself at the moment to offer further data.
I understand but why would it be something with my computer if just one line in the reg file (according to logs) prevents integration, i don't quite understand that part.
I used your guide for years now and never had problems, this is the very first time something from your guide ever failed.
Great Guide by the way thank you for doing all this work and still updating it after years.
 
That doesn't belong here. You're not being productive by trying to help troubleshoot, and this is unrelated to the user's situation and my guide. If you want to share presets please feel free to do so on a thread you start, but making people ask for "hints" and hijacking other people's guides is not the way to go about it.
Fair opinion and tought - and you're wrong as i actually want to help and this is a special case.
 
I understand but why would it be something with my computer if just one line in the reg file (according to logs) prevents integration, i don't quite understand that part...
Please don't take me too literal, as I don't know all the technical bits. Nuhi and others can give better details, but my understanding is when NTLite integrates tweaks it does so locally first. In other words, it creates a file on the computer with a configuration of what should go into the image, and we can see that in the log of HKEY_LOCAL_MACHINE\NLTmp~4ed1dc67~USERHIVE50\ where "NLTmp" means NTLite temporary file I believe.

After that prep work it copies the tweaks into the image, and that's the kind of stuff going on in the background when we see the progress bars in NTLite. If a computer has permission errors, which many computers do and they just fly under the radar most of the time, that's where the failure comes in. When we tell a computer "create this file" the computer says "I tried, but for some reason I cannot" that's when it throws an error.

My attempt at an example would be in the PC game Company of Heroes 1 it used to always record multiplayer games with no way to disable it and that was a huge performance hit. The community workaround (not a good one) was to remove write access to the recordings folder, thus preventing those files from being generated. The problem though, is the game was still trying to record anyway it was just failing repeatedly and filling the logs with errors, but the game still worked.

Windows still functions when bits of it are corrupt and broken, we just don't always see it until we need to use that particular feature, folder, etcetera. Using products like NTLite really brings the broken bits to light. Now, of course this could just be a bug or something else going on, but statistically if it works one day and not another, or on one computer and not another, the data says it's almost always a broken PC that needs reformatting to clean up whatever was wrong and it will work once it is fresh again.
 
Please don't take me too literal, as I don't know all the technical bits. Nuhi and others can give better details, but my understanding is when NTLite integrates tweaks it does so locally first. In other words, it creates a file on the computer with a configuration of what should go into the image, and we can see that in the log of HKEY_LOCAL_MACHINE\NLTmp~4ed1dc67~USERHIVE50\ where "NLTmp" means NTLite temporary file I believe.

After that prep work it copies the tweaks into the image, and that's the kind of stuff going on in the background when we see the progress bars in NTLite. If a computer has permission errors, which many computers do and they just fly under the radar most of the time, that's where the failure comes in. When we tell a computer "create this file" the computer says "I tried, but for some reason I cannot" that's when it throws an error.

My attempt at an example would be in the PC game Company of Heroes 1 it used to always record multiplayer games with no way to disable it and that was a huge performance hit. The community workaround (not a good one) was to remove write access to the recordings folder, thus preventing those files from being generated. The problem though, is the game was still trying to record anyway it was just failing repeatedly and filling the logs with errors, but the game still worked.

Windows still functions when bits of it are corrupt and broken, we just don't always see it until we need to use that particular feature, folder, etcetera. Using products like NTLite really brings the broken bits to light. Now, of course this could just be a bug or something else going on, but statistically if it works one day and not another, or on one computer and not another, the data says it's almost always a broken PC that needs reformatting to clean up whatever was wrong and it will work once it is fresh again.
Thank you for taking your time to answer me.
I guess there could be something wrong and i never noticed because it never manifested itself before.
Anyway i will install Windows fresh tomorrow and try again maybe it works then, it's just a lot of work :(
 
First, try the PowerRun program by Sordum, to save time. It runs NTLite with higher privileges and may be able to override the permission error. That only takes a few minutes, versus a few hours reinstalling Windows. If that works, I would still reinstall Windows and disable Defender before making my final image, because I'd rather have a working system creating a new image than trying to build a house on a broken foundation.
 
Last edited:
First, try the PowerRun program by Sordum, to save time. It runs NTLite with higher privileges and may be able to override the permission error. That only takes a few minutes, versus a few hours reinstalling Windows. If that works, I would still reinstall Windows and disable Defender before making my final image, because I'd rather have a working system creating a new image than trying to build a house on a broken foundation.
OK update from me.
There was something wrong on my Machine you were 100% right you are a saint!
I fresh installed windows with my completely unmodified version of IoT LTSC and registry integration worked without a problem.
But its weird i always set up my pc exactly the same and never had such problems before so there must have been something broken in the background.
Anyways thanks again to everyone helping!
I will now build my new iso and install windows again.
 
Doesn't NTL start in NTLite with higher privilege aka supermodetator - seems to me it does.
But also seems to me, the gamer fanatics having fun around your blog and keep you occupied .
 
Error is surely here

Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
"SystemResponsiveness"=dword:000000064

9 digits instead of the maximum of 8
This is 100% correct i just tried it because i have time right now, after removing the extra 0 it integrates without any problems.
 
nuhi
OK i started everything completely from scratch again this one reg file will still not integrate.
Thank you. Interesting, this could be the UCPD service protection.
To confirm, either comment-out these lines in the Reg_3_Settings.reg:
"ShellFeedsTaskbarViewMode"=dword:00000002 (line 550) under the HKCU ...\CurrentVersion\Feeds key

Or on the host disable UCPD velocity service and its scheduled task, reboot and retry full REG.

Will add detection for this so that the rest of the file is integrated.
Let me know how it goes.
 
Thank you. Interesting, this could be the UCPD service protection.
To confirm, either comment-out these lines in the Reg_3_Settings.reg:
"ShellFeedsTaskbarViewMode"=dword:00000002 (line 550) under the HKCU ...\CurrentVersion\Feeds key

Or on the host disable UCPD velocity service and its scheduled task, reboot and retry full REG.

Will add detection for this so that the rest of the file is integrated.
Let me know how it goes.
Sorry but i cant try this anymore because i followed hellbovines recommendation and installed windows fresh and tried again.
It worked on a completely unmodified fresh install of IoT LTSC.
The weird thing for me is i use NTLite and his guide for years now and never had any problems before and i set up my PC and windows installation 100% identical every time.
But also huge thanks to you for your help and your time answering me.
I will install Windows with my newly created iso now.
 
Sorry but i cant try this anymore because i followed hellbovines recommendation and installed windows fresh and tried again.
It worked on a completely unmodified fresh install of IoT LTSC.
The weird thing for me is i use NTLite and his guide for years now and never had any problems before and i set up my PC and windows installation 100% identical every time.
But also huge thanks to you for your help and your time answering me.
I will install Windows with my newly created iso now.
Yeah you stumbled on an overprotective service which thinks a tool is trying to edit host's settings against their will because it matched the same path while editing an image.
Will improve this, at least warn the user why.

Interesting that on reinstall it worked fine, maybe only a certain build of that Windows has the issue.
 
Yeah you stumbled on an overprotective service which thinks a tool is trying to edit host's settings against their will because it matched the same path while editing an image.
Will improve this, at least warn the user why.

Interesting that on reinstall it worked fine, maybe only a certain build of that Windows has the issue.
I use Windows 10 IoT LTSC so the unmodified version of the iso is quite an old build of windows 10 21H2.
 
Back
Top