I am packaging Articulate-Studio-13 ( Presenter/Quizmaker/Engage) for Windows 7 64-bit.

I am packaging Articulate-Studio-13 ( Presenter/Quizmaker/Engage) for Windows 7 64-bit. I have packaged the application and everything runs fine, But the issue I am coming across is when I try to suppress the update prompt after the application launch's, I have edited the registry to disable the updates but after the system restarts the updates popup for the end user. I will list a few things below.

These 3 are the disable registries


"Silent duration"=dword:00001388

I am also listing the active setup registry that was created

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\Articulate Studio 13]
"StubPath"="Reg import \"C:\\Program Files (x86)\\Articulate\\Articulate Studio\\Articulate_Merge_Registry.reg\""

And this is the Install cmd that was created

"%~dp0studio-13.exe" -s -f1"%~dp0response.iss" -sms

REGEDIT /S "%~dp0-DisableEngageupdate.reg"

REGEDIT /S "%~dp0-DisablePresenterupdate.reg" 

REGEDIT /S "%~dp0-DisableQuizmakerupdate.reg" 

Copy /Y "%~dp0Articulate_Merge_Registry.reg" "C:\Program Files (x86)\Articulate\Articulate Studio\"
Reg import "%~dp0ActiveSetup.reg" 

Thank you for everyone's help

0 Comments   [ + ] Show comments

Answers (3)

Posted by: rileyz 8 years ago
Red Belt

Ok, a bit of advice, if you can and it is possible, you should use the MSI from the setup.exe - thats if there is one stuffed in there somewhere. If not you might want to consider repackaging it. Let us know if you need a hand of pulling out the msi from inside the setup.exe - tip, install it and check event logs for MsiInstaller events (to find out if it has a msi). Technically, you should use a entry point to trigger the populating of the HKCU, as it will be more elegant, ActiveSetup is a last resort tool.

Ok, now your issue above. Not the best way to go about it, but hey ho. Things to check, when the registry importing is being done, is it going to the 32 or 64 bit path? You might want to specify the bitness of regedit so you know what your getting. I suspect your settings are being written to the wrong path?

Taking a step back, install the app and import/create the settings manually to ensure the configuration works before attempting to automate. Do this on a clean VM. I notice your using RegEdit and REG Import - is there a reason to use different utils?

Good luck!
Posted by: vjaneczko 8 years ago
9th Degree Black Belt
My guess is you'll have a reg key of SOFTWARE\Wow6432Node\Wow6432Node\Microsoft\ after the import. Edit the reg file to remove "Wow6432Node\" and try again.  I believe the import is occurring as a 32-bit import so it's adding it into the 'appropriate' area of the registry.
Posted by: apptopack 8 years ago
Red Belt
Does the package have any startup service that trigger updates? If so remove it.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ