Reply to Thread

Re: Win7 64bit registry problem

Thanks for the update !!!

Friedrich

Re: Win7 64bit registry problem

I think this "problem" was nothing to do with Win7 64 bit in particular, but just me trying to install something the operating system didn't allow (and Win7 File Protection is possibly more picky than earlier OS).

Current conclusion: not a problem at all.

Re: Win7 64bit registry problem

Chris,

Thanks for the update! Please keep us posted

Friedrich

Re: Win7 64bit registry problem

Thanks for the reply.

After much unsuccessful trying to get things to work, the customer rolled back to last month's Windows 7 update. Now everything works perfectly again. Installed latest update of my app. No problem.

I'll wait for a bigger sample before coming to any conclusions ;-)

Re: Win7 64bit registry problem

Chris,

The WOW64 subsystem isolates the execution of 32-bit applications from 64-bit applications. That means, Windows 64-bit (XP up to Server 2012 R2) always (and not sometimes) redirects to the "WOW6432node". But this does not cause problems (it's expected and by Windows design).

If you create a 32-bit type install for your 32-bit application and you install into the correct folder then it is not caused by redirection at all. Make sure that you request administrator execution level privileges ("requireAdministrator") and that your ActiveX does not rely on missing dependency files.

Hope this helps a bit.

Friedrich

Win7 64bit registry problem

I have a 32bit app that includes a couple of 32bit .DLLs and .OCXs.
Using SB8 (up to date) this installs updates for the app on one or two hundred PCs, normally no problems.

A couple of people recently have had a problem after updating; get Error 429 (Cannot create ActiveX object) when trying to run the app. They have Win7 64bit. The error would result from .DLL not being registered.

Google search shows others with same problem, and suggestions that Win7 64bit sometimes redirects Registry entries (WOW64 ?) and sometimes this causes problems.

Is there anything I can do when installing to get around this?
(My updates always overwrite and re-register my .DLLs )