Jump to content











Photo

Compatibility Mode in WinPE?

compatibility mode winpe

  • Please log in to reply
30 replies to this topic

#26 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 11 July 2022 - 09:30 PM

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

Attached Files



#27 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 12 July 2022 - 08:54 AM


But forgot to mention before my last post it was tested in Win7PE and it doesn't work, as the PE lacks all required to make it work, also set __COMPAT_LAYER doesn't work in the Win7PE.


Good :), but it still could be two different "things" missing in that PE build.

We know that (on full Windows 7, normal user) HKLM (by itself, without the HKCU) works, right?

But we don't know if (on full Windows 7, SYSTEM) HKCU (by itself, without the HKLM) works and (besides "running as") we don't have (unless I am missing something) a way to actually login as SYSTEM on a Windows 7 (I seem to remember that there is not anything similar to minlogon for 7 :unsure:, maybe some trickery with winsta0 :dubbio::).

Since on full 10 HKLM doesn't work, besides the missing things, in a Windows 10 PE the HKCU won't likely work anyway (only an educated guess).

Whilst the HKCU or HKLM may be somehow "traced" with regmon/filemon/procmon, I have no idea how (if possible) the __COMPAT_LAYER could be traced/checked. :(

:duff:
Wonko

#28 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 12 July 2022 - 10:15 AM

Hi Wonko.

 

I just ran a new test Rambooting my 512 MB Mini-10x64-WB.vhd,  using again GetVer64.exe during the test:

 

HKLM_Layers_x64.reg

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"Y:\\Portables\\GetVer64\\GetVer64.exe"="~ RUNASADMIN WIN7RTM"

 

 

It also worked fine, and got Win7 info, so if using GetVer64.exe it works fine on the Mini-10 VHD using HKCU and HKLM Keys and also from set __COMPAT_LAYER.  So GetVer64.exe should also work fine using a HKLM Key on full Win10x64 OS.

 

But if using GetVer32.exe (32 bits version) it fails on the Mini-10 VHD using HKCU and HKLM Keys and also from set __COMPAT_LAYER. and give Win10 info, and also fails if running it using a HKLM Key on full Win10x64 OS.

 

Then GetVer64.exe is the best option in full Win10x64 OS and Mini-10x64 VHDs.

 

Also made a new Win10XPE_x64.wim and included into it: \Windows\System32\Sdbinst.exe and its respective \Windows\System32\es-ES\sdbinst.exe.mui, also included all Win10 catalogs and Full Win10 Software hive, and this version also fail when running GetVer64.exe after running the HKCU and HKLM x64 reg files, same thing for set __COMPAT_LAYER.

 

So far haven't found a way to make GetVer64.exe get the Win7 OS info when running it in my Win10XPE_x64.wim, no matter if it is booted as SYSTEM or as ADMIN.

 

alacran



#29 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 12 July 2022 - 11:06 AM

To summarize our findings after testing GetVer64.exe and GetVer32.exe:

  1. x64 Apps should run fine using all available Compatibility options in full Win10x64 OS and Mini-10x64 VHDs.
  2. x86 Apps should run fine only in Full Win10x64 OS when using the Compatibility options: manual, HKCU Key or set __COMPAT_LAYER, but not when using the HKLM Key.
  3. x86 Apps DO NOT run fine with any Compatibility option on Mini-10x64 VHDs.
  4. So far x86 or x64 Apps DO NOT run fine with any Compatibility option on Win 10 PEs.

alacran



#30 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 14 July 2022 - 06:38 AM

I just found today an old topic from Nov. 2008 in MSFN: Compatibility mode in WinPE 2 trying to make Compatibility mode work on a Vista based WinPE.  But they were not able to make it work at that time.

As I read, I wasn't bad oriented when I said Sdbinst.exe is an important part of a possible solution, as it is part of a suggestion to test, but it is mentioned there Application Compatibility Toolkit (ACT) is also required.

Application Compatibility Toolkit (ACT) [7.8 MB] is part of Win10 2004 ADK, I tried to download the ADK, or at least the ACT several times but it always says the downloader can't find a required *.msi, so I can't go any further in trying to test myself the suggested possible solution.

 

alacran



#31 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16066 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 July 2022 - 09:04 AM

I still believe you are barking up the wrong tree (as did Tripredacus at the time).

 

So you can download the adksetup.exe from here:

https://docs.microso...r-adk-downloads

 

but when you run it it cannot find the needed installation file? :unsure:

 

It's normal for the stupid Microsoft files, they move the files around all the time and very often break links/paths/whatever all the time.

 

The only thing that you could do is to post on MS own forums, where a clueless MVP will give you a totally unrelated answer :w00t:, and nothing will be done to solve your problem in 99.99% of cases. but it could still be the 0.01% .

 

It seems like they do not provide a standalone package:

https://docs.microso...offline-install

(it would be too d@mn simple)

 

Anyway it could also be a temporary issue? :unsure:

 

:duff:

Wonko







Also tagged with one or more of these keywords: compatibility mode, winpe

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users