JFYI
Good news. GetVer64.exe works fine in my Mini-10 VHD.
Just ran another test Rambooting from my 512 MB Mini-10x64-WB.vhd, and this time using GetVer64.exe during the test:
COMPAT_LAYER_x64.bat
set __COMPAT_LAYER=WIN7RTM
"Y:\Portables\GetVer64\GetVer64.exe"
Worked fine and gave Win7 OS info.
HKCU_Layers_x64.reg
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"Y:\\Portables\\GetVer64\\GetVer64.exe"="~ RUNASADMIN WIN7RTM"
Also worked fine and gave Win7 OS info.
But as in previous test (Post No. 11), COMPAT_LAYER.bat
set __COMPAT_LAYER=Win7RTM
"Y:\Portables\GetVer32\GetVer32.exe"
And HKCU_Layers.reg
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"Y:\\Portables\\GetVer32\\GetVer32.exe"="~ RUNASADMIN WIN7RTM"
Didn't work fine, Please see attached photo.
I noticed \Windows\System32\Sdbinst.exe and its respective \Windows\System32\es-ES\sdbinst.exe.mui are present in the VHD.
But the VHD lacks an x86 (32 bits) version in \Windows\SysWOW64 folder, so I extracted it from the install.wim file and copied it there.
NOTE: There is not a x86 *.mui file in install.wim (also checked in a full 10x64 OS and there is not a x86 *.mui file).
And tested again GetVer32.exe, but same result, so something else is needed to let the 32 bits version work fine in the Mini-10 VHD.
alacran