I managed to remove default Windows sounds - but it looks like theres some remains can make the default Windows startup sound even i don't hear it?
You've 366 removals and i've 815 from my latest working preset.
Maybe I'm rude - but has it ever occurred to you that instead of working on an error starting point like 22000.01 and updating via NTL where the error does not disappear and instead using the latest working version from either MCT or uupdump. I am just asking. And another piece of good advice - run your preset while updating via NTL at the same time is born to failure on a faulty vanilla installation. Been there done that. Run your updates first and save without making ISO - and then open NTL again and run your preset - it changes a lot of things, as running the preset at the same time as updates only changes the things that were originally loaded. Just my modest observations. Thanks.
Load your vanilla - whatever. I prefer latest uup dump as i don't waste time for 2 NTL runs.
Don't load preset.
Integrate updates - nothing else.
Load NTL again and then run your preset to have the NTL ISO you want to install.
Not doing that - you can post 1+ problem again.
Further problems is not NTL but PEBCAK as Clanger use to say
Before you even use NTL you've unpacked you (ISO) image to a folder.
With WinRAR or in Windows handling ISO's and copy paste files to a named folder of choice.
Run NTL - load the image (from unpacked folder named) - goto update tab - integrate updates - run NTL on Apply tab.
Then you don't even create an image (ISO).
Then open NTL again and run your preset.
Further guidelines - go search youself.
The builds coming last in month? - from the settings update you can postpone the updates fixing something which
will come in the regular updates second tuesday every month.
Normally i wait to wedensday from a fixed timeline.
Much easier and timesaving to catch uup's instead of make NTL integrate updates.
But it's a matter of taste and NOT a problem to post.
Since when? I still have it and I only post when I tried to solve it but wasn't able to.
Or maybe they didn't because it was a NTLite/Windows bug.
Good for you.
MAYBE you should look carefully at what you are doing as , you have claimed several times, EVERY image you have created, the issue is there.
SEEING NOT EVERYONE IN THE WORLD HAS THE ISSUE, THEN IT IS YOU !!!!!!