Search results

Hi nuhi, Office 365 desktop apps are not native to ARM64 so we have to install the x86 version, like most apps, hence that's the main reason for stripping down Windows 10 on ARM: to increase performance in the x86 programs (via built-in WOW emulation layer) since native programs are few and far...

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

Fortunately, I've now solved this issue for Outlook: Modern App support > OneCore UAP Common Proxy Stub – 32-bit > Modern App support – 32-bit So that should be added to Microsoft Office compatibility in NTLite, albeit the 32-bit version.

Yep - and only a choice of 3GB RAM on Lumia 950 XL and 1GB of RAM on Raspberry Pi 3 B+

Any specific examples on how each one benefits the standard windows 10 user? Containers, for example, is an alternative to virtualization right albeit more for developers? There is no Win7 option for ARM64, and I'm trying to find out the bare minimum set of components needed to boot Windows 10...

OK, so I narrowed it down to these basic ones for my phone hardware: Audio inputs and outputs Batteries Bluetooth Computer Disk Drives Display Adapters Human Interface Devices Keyboards Mice and other pointing devices Mobile devices Monitors Network Adapters Non-Plug and Play drivers Portable...

Thanks for your reply! Here's the Outlook error when attempting to create profile: All components from Windows Apps have been removed except the following: Out-of-box Experience (OOBE) Windows Apps > Appx Deployment Service Windows Apps > Appx Deployment Service > App Readiness Windows Apps...

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

I'm down to these and managed to get a successful boot with only them: Audio inputs and outputs Batteries Bluetooth Computer Disk Drives Display Adapters FS Compression Filters FS Continuous Backup Filters FS Copy Protection Filters FS Encryption Filters FS HSM Filters FS Physical Quota...

Sometimes the WIM files become corrupt - possibly after injecting a series of drivers after using NTLite. How about these components? Would you expect to get to OOBE without any of them? System > Boot Manager (EFI) System > Device Experience System > Windows Management Instrumentation (Service)...

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

Same question for this component: Network > WLAN > Virtual WiFi Windows doesn't seem to boot up without it? EDIT: booting up now without Virtual WiFi.

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

IKE and AuthIP IPsec keying modules - might be needed for WiFi and definitely for Cellular connection ------------------------------------------------------------------------------- SYSTEM Device Experience - windows 10 won't boot up without it...

Microsoft Edge when connected via Ethernet cable - but not WiFi

Found it - my bad - it was flagged in Compatibility: System > Edge HTML Viewer > Browser window frame (IEFrame) > Browser window frame (IEFrame – 32-bit)

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

Nope - it's back again -seems to happen after RDPing. Update: I managed to get the icons to come back again - possibly onedrive causes it

Seems I've finally nailed it! Should this be added to "recommended" compatibility?

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.