Topic: SysWoW64 - some observations  (Read 832 times)

0 Members and 1 Guest are viewing this topic.

SysWoW64 - some observations
« on: March 08, 2017, 12:05:20 PM »

misty

  • Apprentice
  • *
  • Date Registered: Mar 2017
  • Posts: 8
After porting 5-WoW64 to another WinPE project, I thought I'd post some feedback here. Firstly, well done to everone involved in developing the plugin :worship:

Attempting to run DMDE version 3.20 resulted in the following error on a Windows 8.1 Update 1 based build -
Code: [Select]
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
It ran ok in WinPE's built with other sources. A previous DMDE version (2.8.0) worked ok on Windows 8.1 Update 1. Now it's possible that this doesn't affect the projects here at TheOven. My own WinPE is a very minimal build - the projects here may have additional dependencies. It's also possible that I missed something in the 5-WoW64 plugin when porting it. 

I've managed to port SysWoW64 to a range of different sources - I am however having issues with Windows 10.0.10586.0. Attempting to run any 32-bit applications resulted in error 0xc0000142.

The same programs ran fine on Windows 10.0.15042.0 (Insider preview), 10.0.14233.0 and 10.0.10240.16384 with similar settings (registry entries and file dependencies).

Also I noticed an additional dependency is required in Windows 10.0.14233.0 - ucrtbase.dll. Again, this may not be an issue on builds here.

In regards to the \Microsoft\Windows\CurrentVersion\SideBySide\Winners\ registry entries, I've been building these using variables obtained via wimlib[/b]...

Code snippit -
Code: [Select]
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_ar-sa_575c57e8e91d339b\5.82","","5.82.%Build%.%SPBuild%"
RegWrite,HKLM,0x3,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_ar-sa_575c57e8e91d339b\5.82","5.82.%Build%.%SPBuild%",\
01
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_ar-sa_575c57e8e91d339b\6.0","","6.0.%Build%.%SPBuild%"
RegWrite,HKLM,0x3,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_ar-sa_575c57e8e91d339b\6.0","6.0.%Build%.%SPBuild%",\
01
..........
..........
..........
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings-2014_31bf3856ad364e35_none_d53db4ae58ea8ec9\10.0.%Build%.%SPBuild%","targetNamespace","http://schemas.microsoft.com/SMI/2014/WindowsSettings"
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings-2014_31bf3856ad364e35_none_d53db4ae58ea8ec9\10.0.%Build%.%SPBuild%\Settings","forceFocusBasedMouseWheel","xsd:string"
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\10.0.%Build%.%SPBuild%","targetNamespace","http://schemas.microsoft.com/SMI/2005/WindowsSettings"
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\10.0.%Build%.%SPBuild%\Settings","autoElevate","xsd:string"
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\10.0.%Build%.%SPBuild%\Settings","disableTheming","xsd:string"
RegWrite,HKLM,0x1,"_WinPE_SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\10.0.%Build%.%SPBuild%\Settings","dpiAware","xsd:string"
...this method has enabled me to test other Windows 10.0 builds without any additional work - including build 10.0.15042.0 (Insider preview). Just sharing information and ideas.

:cheers:

Regards,

Misty

Re: SysWoW64 - some observations
« Reply #1 on: March 21, 2017, 10:09:50 AM »

misty

  • Apprentice
  • *
  • Date Registered: Mar 2017
  • Posts: 8
Quote
...I've managed to port SysWoW64 to a range of different sources - I am however having issues with Windows 10.0.10586.0. Attempting to run any 32-bit applications resulted in error 0xc0000142....
Adding the following file resolved this problem -
fwbase.dll

:cheers:

Misty

Re: SysWoW64 - some observations
« Reply #2 on: March 22, 2017, 06:48:25 AM »

JFX

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Dec 2010
  • Posts: 903
Hi misty,

Microsoft is moving a lot of code into *base.dll or *.core.dll files.
To have a good application compatibility you should add all of them to your WinPE.

Re: SysWoW64 - some observations
« Reply #3 on: March 22, 2017, 07:40:29 AM »

misty

  • Apprentice
  • *
  • Date Registered: Mar 2017
  • Posts: 8
@JFX
Thanks for the tip.

Any thoughts on the following (from post #1) -
Quote
...Attempting to run DMDE version 3.20 resulted in the following error on a Windows 8.1 Update 1 based build -
Code: [Select]
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

At first I thought it might be due to the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\ registry entries being for a different service pack build level as the 5-WoW64 Basic plugin is coded for build 6.3.9600.16384. I tried build 6.3.9600.16384 and the same issue persisted. I've also noticed that Dependency Walker is not functioning fully on Windows 8.1 builds - the file dialog will not open.

I do not know enough about SysWoW64 to know whether this is a file dependency or registry dependency issue.

Regards,

Misty

Re: SysWoW64 - some observations
« Reply #4 on: March 22, 2017, 07:55:59 AM »

JFX

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Dec 2010
  • Posts: 903
By SxS error always check the manifest of an application.

This DMDE version 3.2 properly need a newer VCRuntime-

Re: SysWoW64 - some observations
« Reply #5 on: March 22, 2017, 10:44:28 AM »

misty

  • Apprentice
  • *
  • Date Registered: Mar 2017
  • Posts: 8
@JFX
I've traced the problem - please take a look at the registry file 9600_SxS.reg embedded in the 5-WOW64 Basic plugin.

Settings in current file -
Code: [Select]
[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-settings-2011_31bf3856ad364e35_none_315c948a1147b31c]
@="6.3"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-settings-2011_31bf3856ad364e35_none_315c948a1147b31c\6.3]
"6.3.9600.16384"=hex:01
@="6.3.9600.16384"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-settings-2013_31bf3856ad364e35_none_315c66fa1147e65e]
@="6.3"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-settings-2013_31bf3856ad364e35_none_315c66fa1147e65e\6.3]
"6.3.9600.16384"=hex:01
@="6.3.9600.16384"


[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings-2011_31bf3856ad364e35_none_d53df90658ea41e6]
@="6.3"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings-2011_31bf3856ad364e35_none_d53df90658ea41e6\6.3]
"6.3.9600.16384"=hex:01
@="6.3.9600.16384"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings-2013_31bf3856ad364e35_none_d53dcb7658ea7528]
@="6.3"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings-2013_31bf3856ad364e35_none_d53dcb7658ea7528\6.3]
"6.3.9600.16384"=hex:01
@="6.3.9600.16384"


[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55]
@="6.3"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\6.3]
"6.3.9600.16384"=hex:01
@="6.3.9600.16384"


Need to be replaced with -
Code: [Select]
[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings-2011_31bf3856ad364e35_none_315c948a1147b31c\6.3.9600.16384]
"targetNamespace"="http://schemas.microsoft.com/SMI/2011/WindowsSettings"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings-2011_31bf3856ad364e35_none_315c948a1147b31c\6.3.9600.16384\Settings]
"disableWindowFiltering"="xsd:string"
"printerDriverIsolation"="xsd:string"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings_31bf3856ad364e35_none_5e7b0013834d1c8b]

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings_31bf3856ad364e35_none_5e7b0013834d1c8b\6.3.9600.16384]
"targetNamespace"="http://schemas.microsoft.com/SMI/2005/WindowsSettings"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings_31bf3856ad364e35_none_5e7b0013834d1c8b\6.3.9600.16384\Settings]
"dpiAware"="xsd:string"
"autoElevate"="xsd:string"
"disableTheming"="xsd:string"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings-2011_31bf3856ad364e35_none_d53df90658ea41e6]

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings-2011_31bf3856ad364e35_none_d53df90658ea41e6\6.3.9600.16384]
"targetNamespace"="http://schemas.microsoft.com/SMI/2011/WindowsSettings"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings-2011_31bf3856ad364e35_none_d53df90658ea41e6\6.3.9600.16384\Settings]
"disableWindowFiltering"="xsd:string"
"printerDriverIsolation"="xsd:string"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55]

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\6.3.9600.16384]
"targetNamespace"="http://schemas.microsoft.com/SMI/2005/WindowsSettings"

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\x86_microsoft-windows-settings_31bf3856ad364e35_none_025c648fcaefab55\6.3.9600.16384\Settings]
"dpiAware"="xsd:string"
"autoElevate"="xsd:string"
"disableTheming"="xsd:string"

:cheers:

Misty

Re: SysWoW64 - some observations
« Reply #6 on: March 23, 2017, 12:58:39 AM »

JFX

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Dec 2010
  • Posts: 903
Hi Misty,

They should not be replaced, but could be added.
But there is no need. SMI key is handled by SxS_Unknow Section of the WoW64 Plugin.

Re: SysWoW64 - some observations
« Reply #7 on: March 23, 2017, 05:52:46 PM »

misty

  • Apprentice
  • *
  • Date Registered: Mar 2017
  • Posts: 8
@JFX
Looks like I did a very poor job of porting the 5-WoW64 Basic plugin after all. Thanks for taking the time out to clarify my mistake. 

 

Powered by EzPortal