Question

While debugging a browser plugin I noticed that the location of the resource was being abbreviated in Windows 64-bit registry keys. When the registry entry was manually edited to use the long-form path to the resource the plugin started to be recognized.

The DLL is installed to CommonFiles64 and the registry key was added to WOW64 by auto-registering the DLL using InnoSetup.

My question: how to prevent regsvr32 from abbreviating the path to the resource?

For example: I need to prevent the abbreviation of someNicePlugin.dll to someNic~.dll

Was it helpful?

Solution

RegSvr32 doesn't write registry values; it merely loads the DLL and invokes functions the DLL exports. It's those functions that write the values. So it's those functions that need to be changed.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top