Search results

I've decided to end this project now due to time constraints and other commitments, but you guys are welcome to continue hacking Windows 10 based around my ARM experiment that used the commercial version of NTLite. Below are the bare minimum components (besides localisation; undocumented) needed...

The following are already enabled: System > .NET Framework Core > Task Scheduler > Task Scheduler – 32-bit (Time Broker service) System > Credential Manager System > Edge HTML Viewer > Browser window frame (IEFrame) > Browser window frame (IEFrame – 32-bit) Remoting and Privacy > Microsoft...

In particular, which of the FS drivers do we need to guarantee a successful boot?

Without this component enabled I get BSODs such as inaccessible boot device without ever getting to OOBE; does that sound right? Is DHCP Client something that always has to be present? EDIT: booting up now without DHCP Client

I think it's something I removed under System - but don't think it's flagged up in Compatibility. So far I have the following: Office 365 System > .NET Framework Core > Task Scheduler > Task Scheduler – 32-bit (Time Broker service) System > Credential Manager reg add...

Any ideas? I think it's something under system, but it's driving me crazy trying to find out. Initial sign in from unattended.xml OOBE script shows all icons in system tray, such as bluetooth - but when I restart I just see empty black spaces instead of icons.

So far have eliminated System and Windows Apps:

Trying to find out which component is needed... something under system.

System > Recovery Agent > BitLocker Drive Encryption is enabled What other component(s) are needed to protect it? I cannot see it in Control Panel.

So far eliminated: .NET framework (all versions) Internet protocol helper DNS service

This happening in 1903 and 1909. Icons become invisible. Hope to resolve it by this time next week!

This has a big red cross by it in the MMC snap-in. Any ideas which component(s) need to be enabled to protect it? It's not "secondary login" - at least not primarily. Preset attached.

This has cost me about 1 month of trial and error so far to try to figure out why I cannot browse the c drive from another computer: \\192.168.1.159\c$ Working lumia.xml Not working nosmb.xml Both are virtually identical in terms of components! What significant difference exists in the...

I think there might be a bug in the latest release stopping RDP from working.

Is there some foolproof way to safely remove drivers? For example, might we run a PowerShell script to output which drivers are in use - including when we plug in external devices - and use NTLite to strip out the rest?

Start Menu issue: networking and system sections eliminated so far Language pack issue: system section eliminated so far

I am interested in services vs. components and the mechanism by which they are removed from the WIM - the basis for NTLite? For example: TimeBrokerSvc = Task Scheduler wscsvc = Security Center iphlpsvc = IP Helper Dnscache = DNS Client NcbService = Network Connection Broker LanmanWorkstation =...

Need to find out which component removal is causing this.

Any ideas which component is responsible...?

...but other browsers do! I need to try to find out which component needs to be re-ticked to bring this back?