Search results

I stumbled on this as well with my LTSC experiments. Since I DO want the Store and want to run games, I noticed that the newly created WindowsApps folder on my Game SSD is also forcibly encrypted.

Rightly assumed :-) To be honest it doesnt seem like a big deal. Got my LTSC down to 1.6+GB at this point, so far all works as expected!

Think Ill make a habit of keeping these in, not the first time these components cause havoc on my builds on a variety of totally random aspects.

To be fair, Nvidia Control panel has always been a slow bitch to open up. Well you might be right about that compatibility thing, I might have forgotten that one. In that case I'll just have to fix searchui.exe crash. I wonder if some disabled services could be causing it. Ill post my config...

Is this the NTLite build you made the working LTSC + working cortana and lowest size? Currently I tried both latest regular and beta of NTLite and both on latest LTSC iso with all cortana dependencies and Internet explorer in i get the same searchui.exe crash. Also the size is way higher than...

From my experience this is really an issue when removing something related to Internet Explorer or Edge 32/64-bit stuff... I havent had an issue with this since I kept most of this in.

Yea, Speedify VPN network firewall lock is broke still with beta. I assume this must be related to windoww connection manager, very high probability. Ill leave it on then, its not like a major space consuming component. No clue.

Yea. Perhaps cuz the VM time seems out of sync, not really bothered with it though. Im not confident the new beta with removing MobilePC works. Ill get back and report. It might fix that particular service, but still somehow effect networking?

Trying to fix why a VPN program's Network lock didn't work in my Windows 10 build for 2 days, finally found the culprit 'MobilePC' Googling this component just now redirects me back to NTLite website release notes, november 13th patch: "Components: ‘Mobile PC’ removal breaking ‘Windows...

Sadly its something in the component removal on 1511. Can't pinpoint what it is, i applied the same profile as i used on 1607 is when i first discovered it. After that ive been trying to strip from a manual clean point but no luck so far. I'll keep trying. Edit: might be one of the core metro...

"Preparing Windows" hangs to black screen On a 1511 build. What could be the cause of this? I can go to task manager, run cmd prompt and everything, just desktop wont show up.

Ah. I doubt this will be an issue with fast SSD, and I disable pretty much any background process that you mentioned amongst others. Don't think ive used search indexing or anti-virus software in almost a decade :P Sandbox/Virtual machine or virustotal for the win! Thanks!

Hi there! From a technical aspect, stripping drivers from either W7/10 only reduces the iso but doesn't actually increase mem usage / overhead at runtime right? I mean drivers only get loaded when the hardware for it is detected? Can always disable useless devices afterwards. Or is there...

Hi! I'm curious when stripping a non-N version, which basically includes the 'media feature pack' (whereas N version does not), which components (that can be removed) is responsible for this: - Video playback in browser like Firefox (Which require external windows video codec) where Chrome has...

I went with a permanent Win 10 virtual machine (vmware)specially made for NTLite, which I can access from any OS i want. And no more license issues after that.

Well its not that bad, hah. I'd say 10 mins in a VM +overhead with big cumulative update and extreme stripping to 1.5GB iso :p But it gets longer everytime you do a new 'pass' :>

Gotcha :-)

Ok, issue is more widespread than i realised, and not particularly related to my drives/ahci. In example what occurs: - Install Nvidia driver, results in monitor going from PnP to Generic Monitor under other devices. (Causes no problems tho) - Attach USB mass storage (thumb drive i.e. wont add...

But the first one is classified as 'update' and the latter as 'Security update' Why would MS screw up classification naming? I mean, there must be regular OS fixes AND security updates for a specific Windows build, are you saying both regular and security updates are within a single cumulative...

A duplicate? I usually grab the latest 'Regular' and 'Security' cumulative update from Microsoft update catalog if thats what you mean? Unless I made a mistake, I'm human after all :-)