Search results

I'm installing live drivers like this - but it's probably something I've stripped out of the wim with ntlite that's responsible for Bluetooth not quite completing - but it's a minor still: diskpart /s C:\Users\gilius.TRAINING\Desktop\ntlite\i.txt dism /apply-image...

It's something under Remoting and Privacy

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!

That's right - only added administrator account - but there's no user entry box after creating a user under Local Users and Groups post-OOBE.

Infrared is already ticked. If I find out what else is needed I will post here - but for now it's low priority because it's just for acknowledging Bluetooth devices that are already connected and working.

Drivers > Bluetooth Windows Apps > Network Connection Broker System > Windows Push Notification Service (WINS) Hardware support > Devices Row > Device Association Service > Bluetooth But there's also something else needed to officially complete the Bluetooth connection - though devices will...

So far this works: Network > Netlogon > Active Directory System > Secondary login But there's something else that is responsible for the "other user" box appearing on the logon screen.

That TWINUI is confirmed to allow "View online" in the OneDrive context menu: Remote and Privacy > OneDrive Windows Apps > Setting Sync System > Anti-Malware Scan Interface > User Account Control (UAC) System > Windows User Interface (TWINUI) – 32-bit (for View Online context menu)...

This is also very important for 1903/1909 as the context menu can also drop off because of this: "What causes this is quite simple. A few months back, MS changed the way the installer works. Default settings now are per user, and not per machine. If you simply download the OneDrive installer...

One or more settings under System > COM+ API are also needed - otherwise no SIM is detected.

It's something under Network - beginning with the letter N

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.

Damn it was the firewall!!!! I feel like an idiot now... how could I have missed that... I thought c drive was shared by default. I award nuhi a trophy for attention to detail!

OK, on second thoughts - well spotted - soooo.... first thing I am testing is windows firewall removal Second test: browser.internet explorer addition

By default you can browse the C drive of any Windows computer connected on the same network - but you will get prompted for credentials. I haven't made any custom shares for this test - it's just basic SMB connectivity I am testing here. Lumia.xml prompts for password but nosmb.xml does not...

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...

False alarm - not problem with update after all

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?