search

leecher1337 / ntvdmx64

Run Microsoft Windows NTVDM (DOS) on 64bit Editions
823 stars 81 forks source link

Installing (CCPU version) on Windows 11 (Build 2262.2283) causes Sign-on options and other auth-related failures #240

Open rswindell opened 1 year ago

rswindell commented 1 year ago

Reproduced this twice on fresh installs of Windows 11 Pro. After (and only after) installing CCPU build of ntvdmx64 (running usa/install.bat from an admin console), and rebooting:

  1. the Windows Settings->Accounts->Sign-On options just gives an infinite spinning cursor (all online support tips to fix this, don't)
  2. trying to create a folder in ProgramData/Microsoft/Windows/Start Menu/Programs/Startup fails (after UAC, just silently fails)
  3. trying to access Windows/ServiceProfiles/LocalService fails (after UAC, just silently fails)
  4. Google Chrome would fail to install (error 124)

Reverting to a System Restore point just before installing NTVDMx64 resolves all of the above issues.

I tried the HAXM build too, but didn't have the requisite drivers (yes, it's a new Intel Core i7 processor), so I reverted back to CCPU downloaded from http://www.columbia.edu/~em36/ntvdmx64.html (I'm not that performance hungry in this case).

ReddestDream commented 1 year ago

A few months ago, I experienced very similar symptoms on a wide range of Skylake+ and Ryzen laptops running Windows 11 22H2 and Windows 10 22H2.

Something appeared to be going wrong with Authentication generally, causing various options ranging from Defender to UAC to Disk Checkup and parts of Control Panel along with the above-mentioned Sign-On options and some program installers to fail.

Basically, anything that uses/requires UAC just didn't work at all and would silently fail, like no box would ever appear. Creating folders in locations that require UAC authorization would also silently fail as would copying files to protected locations. Even trying to open UAC options itself would fail.

I traced the issue back to ntvdmx64, which I had compiled myself in July after the latest commit. Reverting the last commit didn't resolve it. I tested older versions I had compiled and retained, and the same issues occurred. I was under the impression that some sort of Windows change, local or at the server level, had triggered the issue, and I uninstalled ntvdmx64 from all the affected hardware. I have not tested since. ntvdmx64 was in fact actually working to run DOS programs on the affected hardware despite the above issues. Thanks!

leecher1337 commented 1 year ago

This indicates that there was a symbol update problem for AiOpenWOWStubs symbols. Please delete HKEY_LOCAL_MACHINE\Software\ldntvdm key in registry to enforce reinit of symbol cache. Then you should open 2 apps, i.e. Execute cmd.exe and then start cmd.exe from its prompt, then it should trigger a symbol reload. Afterwards, reboot so that svchost.exe injection reoccurs with correct address.

If this doesn't fix problem Number 1, you can expand the blacklist: Create c:\windows\ldntvdm.ini with the following content:

[blacklist]
FileCoAuth.exe
SearchIndexer.exe