[Windows 11] Some app/feature compatibility requirements

Dazuz

Dazuz

New Member
Messages
7
Reaction score
4
I was poking around and seeing what I can get away with, and thought I'd share the findings with you.

Internet Connection Sharing (ICS)Required for Windows Sandbox.
Hyper-VRequired for Windows Sandbox.
Remote Desktop Services ActiveX ClientRequired for Windows Sandbox.
Trusted Platform ModuleRequired for Easy Anti-Cheat (EAC), specifically TBS.DLL.
Windows Symbolic Debugger EngineRequired for qBittorrent.
Application compatibilityRequired for "Pin to Start" context menu option for .exe files.
Volume Shadow Copy (API)Required for Disk Clean-up tool.
Windows Push Notifications User ServiceRequired for Action Centre (WIN+A).
App ReadinessRequired for default UWP apps to install during Windows install.
Background Media PlayerRequired for Windows Photos to be able to play videos.
Image Color Management (ICM)Required for Paint.NET.
Browser BrokersRequired for "Make default" in browsers to work.
Shell App RuntimeRequired for "Make default" in browsers to work.
Taskbar popups (PC Shell 'Tray Flyouts')Required for "Open with..." context menu option.
Shell Experience HostRequired for clock/calendar/network left click menu/flyout to work.
Network ExplorerRequired for JDownloader2 to display proper file icons and "Set Download Directory" to work.
Browser window frame (IEFrame - 32 bit)Required for (some?) 32-bit programs to open URLs.
Windows Internet (WinINet) - 32 bitRequired for mIRC to start.
Windows Feature Experience Pack - DesktopRequired for search to work.


Installation fails when using Rufus without these:
  • Kerberos Client
  • Text Services Framework
  • Encrypting File System (EFS) - Service
  • Appx Deployment Service
  • Web Account Manager
  • Shell Services
 
Last edited:
Dazuz said:
Installation fails when using Rufus without these:
  • Kerberos Client
  • Text Services Framework
  • Encrypting File System (EFS) - Service
  • Appx Deployment Service
  • Web Account Manager
  • Shell Services
Click to expand...
Are you stating a Rufus-created USB requires these components? Rufus avoids touching the Windows image as much as possible other than to create an optional unattended file to handle install options. Besides adding the boot loader, it's simply extracting the image to a newly created volume.

In general, several of the above components are required for normal Windows operation (regardless of Rufus).
- Kerberos Client (for session security)​
- Text Services Framework​
- Appx Deployment Service (for a working desktop and default apps)​
- Shell Services​
 
For installation, there's no need (without Rufus)
Text Services Framework (needed to enter the Wi-Fi password when choosing the SSID among other things)

And when we tested with W11 22h2 :

Shell Services (needed for Settings - System - About), no problem for installation
Appx Deployment Service (needeed for installation and Settings - Personalize - Theme)
App Readiness, no problem if you don't use the related compatibilities, adding/installing new Apps, etc... (to be deleted in Live only, to use the Apps already present when Windows is installed)

No retest Appx Deployment Service and Shell Services with 24h2
 
garlin said:
Are you stating a Rufus-created USB requires these components? Rufus avoids touching the Windows image as much as possible other than to create an optional unattended file to handle install options. Besides adding the boot loader, it's simply extracting the image to a newly created volume.

In general, several of the above components are required for normal Windows operation (regardless of Rufus).
- Kerberos Client (for session security)​
- Text Services Framework​
- Appx Deployment Service (for a working desktop and default apps)​
- Shell Services​
Click to expand...
Technically it has nothing to do with Rufus, it's just that the windows install fails in a way or another without them. I've been using Rufus with its tweaks for live installs for a couple of convinience reasons, so that's why Rufus was included.

With NTLite's Unattended install the process finishes without some of them at least, but then there's other problems.

tistou77 said:
For installation, there's no need (without Rufus)
Text Services Framework (needed to enter the Wi-Fi password when choosing the SSID among other things)

And when we tested with W11 22h2 :

Shell Services (needed for Settings - System - About), no problem for installation
Appx Deployment Service (needeed for installation and Settings - Personalize - Theme)
App Readiness, no problem if you don't use the related compatibilities, adding/installing new Apps, etc... (to be deleted in Live only, to use the Apps already present when Windows is installed)

No retest Appx Deployment Service and Shell Services with 24h2
Click to expand...
Oh, should have pointed out it was tested on 24H2.
 
Dazuz said:
Oh, should have pointed out it was tested on 24H2.
Click to expand...
Yes, us too, except for Appx Deployment Service and Shell Services that I did not do (keeping these components)

EDIT : For Text Services Framework, I confused it with another component
Removed in Live, not tested with 24h2 in Offline
 
Last edited:
Shell will not work if these are removed.
Kerberos Client or File Sharing Support (SMB Common)
 
garlin said:
Are you stating a Rufus-created USB requires these components? Rufus avoids touching the Windows image as much as possible other than to create an optional unattended file to handle install options. Besides adding the boot loader, it's simply extracting the image to a newly created volume.

In general, several of the above components are required for normal Windows operation (regardless of Rufus).
- Kerberos Client (for session security)​
- Text Services Framework​
- Appx Deployment Service (for a working desktop and default apps)​
- Shell Services​
Click to expand...
but isnt the "Web Account Manager" not also important for users ?
 
CodeBro said:
is that really nessecary for it, lol?
Click to expand...
I could delete it after changing the image, but I'm not thinking about it lol
But now that I think about it, I believe there's another reason to keep it, but I can't remember, I'd have to test it again.
 
If remove the Web Account Manager, the Windows will not install (even with the autounattend.xml file) - there will be an endless reboot.
Can remove it after installing the system.
Why such components are not blocked from remove in the NTlite, just like the EFS service for example, is a mystery to me.
 
Last edited:
ExDeF said:
If remove the Web Account Manager, the Windows will not install (even with the autounattend.xml file) - there will be an endless reboot.
Can remove it after installing the system.
Why such components are not blocked from remove in the NTlite, just like the EFS service for example, is a mystery to me.
Click to expand...
Good to know maybe they will add IT in the next Version Update
 
ExDeF said:
If remove the Web Account Manager, the Windows will not install (even with the autounattend.xml file) - there will be an endless reboot.
Can remove it after installing the system.
Why such components are not blocked from remove in the NTlite, just like the EFS service for example, is a mystery to me.
Click to expand...

Just like EFS, Web Account Manager is locked by OOBE Compatibility. In general, NTLite does not prevent removal of a component just because it will break something.
 
tharri said:
Just like EFS, Web Account Manager is locked by OOBE Compatibility. In general, NTLite does not prevent removal of a component just because it will break something.
Click to expand...
I removed OOBE component from the image and there were no problems with the installation, the necessary files were protected.
By the way, EFS is required for installation.
 
tharri said:
Just like EFS, Web Account Manager is locked by OOBE Compatibility. In general, NTLite does not prevent removal of a component just because it will break something.
Click to expand...
Print 3D, Microsoft Account are also locked for OOBE, but if you remove them it does not interfere with system installation.
Needs to be done: Web Account Manager, EFS - locked for Windows Setup and Deployment, not just OOBE.
 
Last edited:
ExDeF said:
Print 3D, Microsoft Account are also locked for OOBE, but if you remove them it does not interfere with system installation.
Needs to be done: Web Account Manager, EFS - locked for Windows Setup and Deployment, not just OOBE.
Click to expand...

Yes, it seems then the problem is they are misclassified, at least on Windows 11.

I was under the impression that you thought they should be marked as not removable under any circumstances. I was simply stating that in general, that is not NTLite's approach.
 
You must log in or register to reply here.
Back
Top