Strange behavior between IE 8 or IE 9 and Windows Explorer

Hello folks,

I have noticed a strange behavior between between IE 8 or IE 9 and Windows Explorer after recent updates on Win7PE_SE. When I open IE 8 or IE 9 all the Internet PAges that require a text input like Google, for instance, doesn't work at all. I write the string to be searched and nothing happens even if I click enter many times it doesn't work.

One thing that "fixes" the problem is to run Windows Explorer at least one time before opening IE 8 or IE 9. I have made a capture before opening Windows Explorer and after opening it and the Registry is attached to this message. I have run the attached Registry_Fix before opening IE 8 or IE 9 and it fixed the problem which means that the real fix is inside the registry entries on that file, but I haven't found the right one yet. I have attached my build log to this message too.

This strange behavior has never happened before. So, I ask: has the Windows Explorer script changed recently? Do you know of any recent changes that could cause this issue?

Best regards,

Aeolis

Hello folks,

After doing a bit of debugging I think the problem is with Copy Files script version 45. It is unable to copy some winsxs windows controls files. As you can see below:
 

Code: [Select]

   (1-files.Script) FileCopy [%BaseDir%\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\manifests\*_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_pt-BR*] to: [%BaseDir%\Target\Win7PESE\Windows\winsxs\manifests]: No matching file found
   (1-files.Script) FileCopy [%BaseDir%\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\manifests\*_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.7601.17514_pt-BR*] to: [%BaseDir%\Target\Win7PESE\Windows\winsxs\manifests]: No matching file found
   (1-files.Script) FileCopy [%BaseDir%\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\manifests\*_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_pt-BR*] to: [%BaseDir%\Target\Win7PESE\Windows\winsxs\manifests]: No matching file found
   (1-files.Script) FileCopy [%BaseDir%\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\manifests\*_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7601.17514_pt-BR*] to: [%BaseDir%\Target\Win7PESE\Windows\winsxs\manifests]: No matching file found

After doing some research in the folder adreess used by the File Copy script I've found the right adresses should be:

amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.7600.16385_pt-br_bbf27855f153915b
amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_pt-br_120bd26cb05db282
x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.7600.16385_pt-br_039faf2d05cfba61
x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_pt-br_59b90943c4d9db88

The ones with the tags "5.82.7601" and "6.0.7601" are below:

amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9
x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af
amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac
x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2

I was unable to find references to tags "5.82.0.0" and "6.0.0.0". I hope it helps.

Best regards,

Aeolis

Hi Aeolis

I checked relative to my sources SP0 (7600)/SP1 (7601) fr-FR, en-US, my previous mod to copy only the DistLang resources seemed fine here.
and I have here manifests versions "5.82.0.0" and "6.0.0.0".
Something strange, it seems that you have a mixed between the common-controls: comctl32.dll (7601-SP1) and the language file controls.resources comctl32.dll.mui (7600-SP0)!

Regardless, in all cases, to ensure that there was no problem and for a better compatibility, I returned backwards as it was before, by copying all controls.resources language (only 700kb)
It should be better for you.

Hello folks,

Thank you ChrisR! I have searched my Windows 7 Utimate x64 and x86 bit images (pt-BR) and could find the 5.82.0.0 and 6.0.0.0 references inside winsxs folders in both install and boot sources. They are below:

5.82.0.0 References:

Code: [Select]

==================================================
Filename          : amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_en-us_0a5df035e455a518.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\boot_wim\2\Windows\winsxs\Manifests
Size              : 792
Modified Time     : 20/11/2010 18:24:01
Created Time      : 20/11/2010 18:24:01
Last Accessed Time: 20/11/2010 18:24:01
Attributes        : C
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : AM2FB2~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_en-us_0a5df035e455a518.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\Manifests
Size              : 792
Modified Time     : 21/11/2010 07:36:25
Created Time      : 21/11/2010 07:36:25
Last Accessed Time: 21/11/2010 07:36:25
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : AM2FB2~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_en-us_520b270cf8d1ce1e.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\Manifests
Size              : 788
Modified Time     : 21/11/2010 07:36:27
Created Time      : 21/11/2010 07:36:27
Last Accessed Time: 21/11/2010 07:36:27
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8C572~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_en-us_520b270cf8d1ce1e.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x86\sources\boot_wim\2\Windows\winsxs\Manifests
Size              : 788
Modified Time     : 20/11/2010 14:00:49
Created Time      : 20/11/2010 14:00:49
Last Accessed Time: 20/11/2010 14:00:49
Attributes        : C
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8C572~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.0.0_en-us_520b270cf8d1ce1e.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x86\sources\install_wim\5\Windows\winsxs\Manifests
Size              : 788
Modified Time     : 21/11/2010 00:32:17
Created Time      : 21/11/2010 00:32:17
Last Accessed Time: 21/11/2010 00:32:18
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8C572~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

6.0.0.0 References:

Code: [Select]

==================================================
Filename          : amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_en-us_02bf32cb04699123.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\boot_wim\2\Windows\winsxs\Manifests
Size              : 790
Modified Time     : 20/11/2010 18:23:51
Created Time      : 20/11/2010 18:23:51
Last Accessed Time: 20/11/2010 18:23:51
Attributes        : C
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : AM6EE4~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_en-us_02bf32cb04699123.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\Manifests
Size              : 790
Modified Time     : 21/11/2010 07:36:16
Created Time      : 21/11/2010 07:36:16
Last Accessed Time: 21/11/2010 07:36:18
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : AM6EE4~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_en-us_4a6c69a218e5ba29.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x64\sources\install_wim\4\Windows\winsxs\Manifests
Size              : 786
Modified Time     : 21/11/2010 07:36:16
Created Time      : 21/11/2010 07:36:16
Last Accessed Time: 21/11/2010 07:36:18
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8B0A3~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_en-us_4a6c69a218e5ba29.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x86\sources\boot_wim\2\Windows\winsxs\Manifests
Size              : 786
Modified Time     : 20/11/2010 14:00:47
Created Time      : 20/11/2010 14:00:47
Last Accessed Time: 20/11/2010 14:00:47
Attributes        : C
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8B0A3~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

==================================================
Filename          : x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.0.0_en-us_4a6c69a218e5ba29.manifest
Folder            : G:\Win7PE_SE\[Imagens]\Win7_x86\sources\install_wim\5\Windows\winsxs\Manifests
Size              : 786
Modified Time     : 21/11/2010 00:32:13
Created Time      : 21/11/2010 00:32:13
Last Accessed Time: 21/11/2010 00:32:13
Attributes        : AC
Extension         : manifest
Duplicate Number  :
Duplicate Group   :
File Position     :
File Content      :
Short Filename    : X8B0A3~1.MAN
File Owner        : BUILTIN\Administradores
==================================================

I am struggling with a MS Visual C++ Runtime problem to run Privatefirewall script after recent updates on WIn7PE_SE project. I am debugging it right now. See you soon.

Best regards,

Aeolis

In the last MS Visual C++ Runtimes script, I recently added two options to try to lighten VC++2005(8.0) and VC++2008(9.0).
VC++2010 and VC++2012 easier, remains unchanged.

By default only the latest Versions 8.0.50727.6195 and 9.0.30729.6161 are used with news checkbox Lite(latest) enabled.
This should be sufficient for many apps but not for all.
I guess that your Privatefirewall need other versions, you can probably disable Lite options to get "all" Runtime versions, the same that in the previous script

Here Sizes, depending on the options (displayed in tooltip)
Visual C++ 2005 (8.0). . . .   x86: 20MB   / x64: 35MB    / Total: 55MB"
(8.0) Lite (latest) . . . . . . .    x86: 4.5MB  / x64: 6.2MB   / Total: 10.7MB"
Visual C++ 2008 (9.0). . . .   x86: 54MB   / x64: 58MB    / Total: 112MB"
(9.0) Lite (latest). . . . . . . .  x86: 9.5MB  / x64: 12.3MB / Total: 21.8MB"
Visual C++ 2010 (10.0). . . . x86: 12MB   / x64: 15MB    / Total: 27MB"
Visual C++ 2012 (11.0). . . . x86: 11MB   / x64: 14MB    / Total: 25MB"

Hello folks,

Once more, thank you very much ChrisR. I am already using the MS C++ script with all components (little version check boxes are unchecked), but the problem persists. I need to debug it deeper, but for now I think it's a problem with WoW64, it looks like the applications can't see their WoW64 dependencies clones. All dependencies called by the applications (Privatefirewall and a few others like IE9) in my build are there, but dependency walker tells me they are the wrong architecture for the applications, even if the x86 and x64 files are there.

I think it could be a problem with missing Registry entries that points to WoW64 files when searching for their System32 clones.

Sorry if I couldn't make myself really clear for now. I am a bit sick and very tired, but as soon as I get better I'll be back to my debugging routine.

Best regards,

Aeolis

Hello folks,

I have came back with more debugging information about the issue. The problem is that I have detected after recent updates some application having problem loading its dll, for now I will limit the problem to a specific case which is Privatefirewall.

I have successfully installed and run Privatefirewall inside Win7 PE SE x86 and x64 builds for some time before the recent updates. What I trying to do here is to debug what have changed since them to fix it and make Private firewall run ok again.

I have detected that what prevents "PFGUI.exe" from running (PFGUI.exe is Privatefirewall GUI - the Privatefirewall services runs Ok, but without GUI user cannot configure and receive alerts) is that one of the two dll that are registered at program start up using "regsvr32.exe /s capicom.dll" and "regsvr32.exe /s SSCProt.dll" commands cannot register with error of "check if the file path is valid..." it seems that the file can't be seen. Using that approach SSCProt.dll can successfully be registered, but capicom.dll can't.

I have done some research using ProcMon and Dependency Walker. The log file for ProcMon and the files for Dependency Walker are attached to this post as well as my build log. After looking into ProcMon I could not find missing file dependencies, but saw some WOW64 registry alerts which I cannot interpret because of my lack of knowledge about the subject. After looking into Dependency Walker logs I have seen that are some problems with alerts of missing file dependencies related to the right architecture regarding the capicom.dll and SSCProt.dll. I have searched into my build and both x86 and x64 files are there.

It looks like the capicom.dll and SCProt.dll can't "see" the correct architecture files even if they are really there (and they are there). I hope somebody, maybe JFX with his WOW64 knowledge can help here.

Best regards,

Aeolis

Dependency Walker files aren't very useful as they only represent the import of the selected file.

Are you sure you use the right regsvr32.exe, the one in Syswow64 folder?

Hello folks,

Dear JFX, thank you for your attention. Yes, I am sure I have used the SysWOW64 files (regsvr32.exe, capicom.dll and SSCProt.dll). I know Dependency Walker files have not much use that is why I have provided Process Monitor log file too.

If you need any extra information just let me know.

Best regards,

Aeolis

Hello folks,

I would like to report that the issue I have mentioned before as far as I could check is limited to x64 builds. I have successfully build a x86 PE and Privatefirewall run successfully as well as other applications. That leads me to think that the problem is really related to WOW64. The build log is attached to this post.

Best regards,

Aeolis

Well process mon log show that following files are missing in SysWow64 folder:

SSCProt.PTB
SSCProt.PTB.DLL
SSCProt.PT
SSCProt.PT.DLL

wscisvif.dll
ncrypt.dll

Make sure your script copying them.

@Aeolis

Quite away from subject, it seems subject goes from ie to Privatefirewall...
just a reminder, extracting Privatefirewall setup file as I proposed much more earlier might gave c++ files.. as in some other apps....
anyway,

Just a mini syntax touch, Following JFX, This may help

Code: [Select]

//Dependencies
Set,%PluginArch%,x86
Require_FileQ,wscisvif.dll
Require_FileQ,ncrypt.dll

http://theoven.org/index.php?topic=43.0

Hello folks,

@Lancelot: Thank you. I have see your suggestions and updated my code a few time ago (in all my scripts). Thank you again.

@JFX: I have added the files you have mentioned, but it does not fix the problem and I keep receiving a MS C++ Runtime error every time I run "PFGUI.exe". Mainly I think it's because "capicom.dll" can't be registered in x64 build. I will use Process Monitor once more and dig deeper. I will be back soon with more information. Just to inform x86 builds are ok.

JFX how did you find out in ProcMon log the missing files? I did a filter > Result > LoadImage and looked for error in LoadImage results. Is that the best way?

Best regards,

Aeolis

sth:
My experience showed me,
some x86 applications compatible to hostx64, they require c++ files, and their setup mostly contain them too,
and so far, copying these dll files to syswow64 folder is enough on hostx64 case

Giving example, following lines to from WinMerge Plugin (\Gena\Apps\File Tasks\) :

Code: [Select]

If,%sourcearch%,Equal,x86,Set,%targetdirvalue%,%target_sys%
Else,Set,%targetdirvalue%,%target_win%\SysWOW64
//-
Set,%t%,%ProjectTemp%\TempExtractFolder\%ProgramFolder%
Call,FileCopyBiggerVersion,%t%\{sys}\mfc71.dll,%targetdirvalue%
Call,FileCopyBiggerVersion,%t%\{sys}\mfc71u.dll,%targetdirvalue%
Call,FileCopyBiggerVersion,%t%\{sys}\msvcp71.dll,%targetdirvalue%
Call,FileCopyBiggerVersion,%t%\{sys}\msvcr71.dll,%targetdirvalue%

Further Good Luck 

JFX how did you find out in ProcMon log the missing files? I did a filter > Result > LoadImage and looked for error in LoadImage results. Is that the best way?

Every file access begin with the CreateFile API, so only include this operation.

The system will look in different paths for the dll. If there is no success then the dll was not found anywhere.

There are files that will always been show as missing like: wow64log.dll or rpcss.dll
Or sometimes resources files, cause not all windows versions are fully translated

Hello folks,

Thank you JFX, Lancelot and ChrisR! It was really a missing dependency in SysWOW64 folder. The last one was "bcrypt.dll". Now the script is working as expected. For now I will test it a bit more and release it later.

Best regards,

Aeolis