After some testing...you're correct. It's absolutely a driver. I also had to keep "Pseudo-locale" under Localization > Language as well. Keeping all drivers and not keeping that, ended with the same sad face error upon boot. Aside from "Pseudo-locale" & "Virtual Disk Service" under System...
Importing into a fresh Windows 10 v1809 generates an error (the blue screen sad face error) upon booting into setup. Luckily there's waaaay less items inside boot.wim to sort through. Investigating further...
Is there a preset floating around the forums? Maybe one of the presets mentioned in this thread? (I would like to compare and contrast)
Better yet, is there a baseline minimum compoents for boot.wim to function?
I basically have the exact same question as tistou77 in the very firsst post of this...
Again, a novice mistake! Cortana clearly states "Locked by compatibility: Shell Search" & "Depends on: Windows Search". I just didn't interpret that as Cortana is needed for Search. Anyway, thanks for the clarification. The notes within NTLite should've been enough for me to accomplish my...
garlin Thank you! You were the EXACT user I’d hoped would chime in. Swiftly too! Amazing. So, Cortana is also needed for search on 1809 as well? I read a thread that mentioned that but was convinced it was in later releases that required Cortana. I suppose I was incorrect. Also a huge facepalm...
I've been crafting a "Lite" Windows 10 for a few weeks now. I'm ironing out the fine details but 2 particular things are giving me trouble.
* My integrated trackpad doesn't funtion (I2C HID Device & HP Wireless Button Driver inside Device manager have Yellow !)
- Windows cannot start this...
FYI...for anyone who wants to view Protected Components without selecting them in the "Compatibility" section. Open 2 simultaneous sessions (premium feature) of the image your editing. In the 2nd instance select all components in the "Compatibility" section. Now all components which would be...
You’re almost correct. Yes the information I seek IS in the “Extra Info” section but ONLY IF I have a compatibility component checked. I would like to see that information WITHOUT toggling a component protection. When I toggle a component protection to “on” it will automatically reselect any...
Curious if the issues zyr3344 mentioned above were rectified? Mostly want to know if I should make some reg keys before finalizing my ISOs.
After applying changes in NTLite but not creating the ISO, would the registry hive contain the aforementioned settings tweaks after removal of components?
I've identified the required files to keep so the default Mouse Pointer scheme (Aero) stays intact. The "Precision Select" & "Text Select" Aero scheme pointers utilize the "Default Scheme" images therefor they are not in this list. They are in the order they appear in "Mouse Properties" <...
That information is only there if you have a corresponding "component functionality" checked. I do wish it was always available to read in the "Extra Info" section, or even another section specifically for stating what would be protected. Instead of having to select a component to protect, then...
Title mostly says it all. Is there a list of the protected components for each of the selections displayed below "Component functionality" inside the "Compatibility" menu?
My first thought was to open multiple instances of NTLite. Mark everything for removal without anything checked under...
I wanna just chime in. I know this doesn't necessarily pertain to "home users" but I remembering getting wild with driver removal. Doing MANY trial and errors. I definitely ran into 2 issues that were harder than others to track down. I needed an HP (non-microsoft) printer driver to install the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.