x86 ltsc 2038 build - help needed to complete (W10 22H2)

Status
Not open for further replies.
There is also the problem with the Bitlocker driver which is still loaded into the kernel even though the intention is to remove that bitlocker

So this is a Feature Request nuhi please add Bitlocker removal

Manually delete from lower filters ?

Unused Kernel Drivers MUST GO !!!!
 
Last edited:
Damage report this removal broke the start menu (Capability Access) and the Intel1000 (net1i32.inf) in the vm

Interrupts and DPCs are still pretty high, something is broken possibly by MS themselves. What a cashgrab this OS is.
Its the mose movements that make the interrutps and DPCs go high.
VMware workstation latest.
 

Attachments

Last edited:
Damage report
intel 1000 working
Start Menu NOT working (Capability Access)
PowerShell 7 installation Not working - requires Windows Management Framework 4+
Installation size: 3.9GB woohoo (1GB is swap)
 

Attachments

Last edited:
nuhi so PowerShell removes WMF as well ? I would like to remove PS1/2 but keep ability to install ver 7 / latest after.
 
I sense an undocumented overlap between Compatibility locks and removal sets.

So this is the innovation that needs to be pushed. More precision.
 
Yep turned On Windows Store compatibility, start menu started working right away!. (Capability Access)

OK nuhi bro we need CONTROL over the OS but also we need to KNOW what NTLITE IS ACTUALLY DOING, OK ?!

Make it happen.
 
Last edited:
Start menu broken again by another component
PS 7 working
Installation size is larger than before ?
Settings and Control Panel System-not working
 

Attachments

Please know I only mean this constructively, but it's time to take a step back and evaluate where this is going, because right now it's just a play by play of stuff that isn't well defined, due to reasons explained below and by the other veteran's replies. Please understand that the following isn't just intended for the thread starter, but for all the lurkers in this same boat, of which there are many.

POLISHING AN IMAGE
We get these threads every week, and nobody is going to take the time to make an ISO for you, using your works in progress. It's just too much, because presets like this are huge and full of issues, which is why we make posts like these (link1, link2, link3) to help people work through their problems and learn how to do troubleshooting on their own, because that is far more efficient for everyone involved.

It's not because we don't want to help, but rather we're all volunteers, except for the NTLite developer (Nuhi), so unless someone wants to start paying us to do image polishing (link4), people need to either take the advice of the veterans or ignore us and forge ahead on their own, but please don't ask for help on things we've already beaten to death on this forum, such as testing in layers and other basic quality control.

To fix a thread like this is pretty easy, it simply requires time and effort to test the layers. What I mean is, split this into multiple images, testing only your component removals and see what breaks, then make another with only your registry tweaks, etcetera. When you discover which layer presents the problems then you can start narrowing in on the culprit much faster and easier, since we don't have to waste time sifting through a bunch of massive layers that aren't part of the issue. To grasp this concept better, follow along with the steps in that polishing link above.

Everyone puts themself into this situation the exact same way, by doing the shotgun approach and adding hundreds of tweaks simultaneously, and then it doesn't work, so they ask us for help, but the answer is right in front of them--it's too much at once. Also, we already have a number of public presets (link5) that accomplish the same goals of threads like these, which have been vetted and can be used as-is or act as springboards to build on, saving a lot of time and frustration by not reinventing the wheel over problems we've already solved.

After looking at this bigger picture, go back and polish an image to remove all the operator error, then take the time to compile a list of things that appear to have solid evidence pointing to issues with the NTLite tool and report those with an explanation on how to replicate the issue and why you feel like it's a problem in the tool, rather than being due to overzealous tweaking or other operator error.
 
Last edited:
you ARE helping , the silence is functional, I do my test, I post my result, I request additional logic to be programmed into the product.

Simple.

So I broke the Start Menu with another component and will try to bring it back again.

I have some interesting ideas how the image can be slimmed.

There are differences with older presets because MS updated some things so its trickier but for sure I can see if the older presets remove stuff I can also remove.

Ive been using ntlite and nlite since forever I notice the product lacks certain features and logic which will make it much easier and functional.
 
If you've been using NTLite "since forever", why are you having so much difficulty?

You can have "interesting ideas", but NTLite is component based. Either your removals work or it doesn't. Sometimes there might be dependencies that can be addressed, but posting random progress reports doesn't help anybody improve the product.
 
What a classic gaslighting peoples.

Better keep your quiet and let me slim this btch down.
 
Status
Not open for further replies.
Back
Top