HM100

Also, WIN+L causes Validation OS to lock up with the mouse cursor only appearing in the black screen without any window present (Such as CMD) with the only way to exit the OS is to long-press the Power Button which is what I usually do to exit Validation OS. Also, I haven't found a way to capture screenshots from Validation OS without using a VM And I have managed to run the following non-console apps from Windows 11 in Validation OS without issues, to further prove that Win32 apps that are not console-based can run on that OS (The commands you have to type are bold and green for 1sy Party apps while for 3rd Party Apps are bold and red): Windows Font Viewer (Only viewing support is available) "D:/Windows/System32/fontview.exe" lucon.ttf System Information (Some functions cause the app to be non-functional such as the about box because a lot of needed features are missing and can also act as a list of running applications for Validation OS) "D:/Windows/System32/msinfo32.exe" Windows Features (Runs but nothing to enable/disable) "D:/Windows/System32/OptionalFeatures.exe" Printer User Interface (Fully Functional but stub anyways) "D:/Windows/System32/printui.exe" File Signature Verification (Only Advanced is not working) "D:/Windows/System32/sigverif.exe" Driver Verifier Manager (Fully Works) "D:/Windows/System32/verifiergui.exe" CrystalDiskMark (Interface must be set to English or else it bug out, with Greek it would not show Greek characters) "D:/Program Files\CrystalDiskMark8\DiskMark64.exe" You can try these under Validation OS to prove that Win32 apps can run in it. Currently, only 6 apps found in the System32 folder of the main OS drive ran without issues. Also, three fonts can be found at Validation OS: System, Terminal and Lucida Console. Adding just the Marlett font into the VOS Image will make the OS display more badly as most areas will be shown in the Marlett font. Last but not least, unlike the 64-bit WinPE, you can run 32-bit apps on the 64-bit Validation OS (VOS does not come in 32-bit variant but comes in either 64-bit in either AMD64 or ARM64 architecture). Calculator from Windows XP did run under Validation OS (And ran even without any optional component installed) but not under Windows PE.

1. Narrator will not work. Not sure about Audio as I couldn't hear any sound in that OS 2. CMD is opened. But when you close it, another instance is opened automatically Not sure about it yet?

This happens because that OS ships with only two fonts (System and Lucida Console). The Scrollbar buttons and the Titlebar buttons are supposed to render using the Marlett font which is not present in Windows 11 validation OS (But is on Windows Preinstallation Environment/Windows Recovery Environment) and as a result, they're rendered using the same font used in the console window (Lucida Console) which reveals up certain numbers and lowercase latin letters. Titlebars are rendered using System font. When you try to launch those apps you mentioned, they don't launch or they show an error window that says that the app is not compatible? Also, that OS ships with other apps or only with the command prompt? Also, most of the apps such as notepad that can be found at Windows PE are also missing in Windows Validation OS Also, my experience on that OS thought that: Most apps didn't worked (Most Console variants of them loaded properly, with a few exceptions such as the Nircmd Console version which did not worked at all, giving the inability to capture screenshots of the OS). Some apps did caused the cursor to become busy (Such as Mozilla Firefox) but did not launch actually. Some refuse to launch, including registry editor (From the primary SSD drive of course) Basic Diskpart support is available by adding the Disk Management addon. You can use it to view the disk partitions for instance. Command Prompt's Settings could not be changed (And as such you're stuck with black background color and green text color in CMD) Closing CMD will cause a new one to appear CTRL+ALT+Delete shows an error but closing it returns to CMD I can access my laptop's drives using the dir command (The more modular tree command does not appear to work) or using direct paths (Primary Drive was assigned to letter D: while Data ones to E:) If Multiple windows are open and Alt+Tab keyboard combination is used, the classic ones is shown, just like Windows PE Aero Snap works like Windows 7 to 8.1 and is shown without translucent effects Due to a lot of missing resources, it falls back to a broken classic theme (Lack of Aero.msstyles, Marlett font). Text is shown using the System Font in most cases. More info may come once I found more testing on my side, those are fine for now