EDN Admin
Well-known member
I have a 32-bit Windows Explorer.exe shell namespace extension that cannot be converted to x64 because is uses several 32-bit 3rd party controls that are not going to x64. On a 64-bit machine, I add a shortcut to the Desktop with this as the target:<br/><br/>C:WindowsSysWOW64explorer.exe /separate, /e, ::{B3C4063F-5A41-11D3-896F-0060974C6D91}<br/><br/>This shortcut works on x64 XP, Vista, 2003, and 2008R1. Additionally, it worked on the Windows 7 betas. However, something changed with the RTM version of Windows 7.<br/><br/>When I double click my shortcut, I can see the 32-bit version of explorer run very briefly in Task Manager before it kicks off a 64-bit explorer.exe and exits. Obviously my 32-bit namespace cannot be loaded in an x64 process, so there is my problem.<br/><br/>I have looked all over the web and Microsoft sites but have not found a resolution to this problem. Does anyone know why this is happening and, more importantly, how I can get the 32-bit explorer.exe process to run with my namespace?<br/><br/>Thanks,<br/>Tim
View the full article
View the full article