Hi Rune, Thanks for the "confirmation" that it is not just me! I Have an open support incident with Flexera that is showing as "Escalated", but its been nearly 2 weeks since i actually raised the issue and they have not requested anything beyond my initial submission which included installer logs showing a success and failure on the same machine. I'm hoping they know what the problem is and are working on fixing it 😉 I will update if/when i known anything else. Regards, /SiD ... View more

Also confirming that making this change resolves the issue. Thanks. /SiD ... View more

Just to add my voice, Me Three. Running on Windows 8 Enterprise x64. Either of you guys under maintenance and raised a service request? ... View more

I can confirm that making the registry change described in the article allows me access to network drives. Does not explain the difference in behavior between Windows 7 & 8! ... View more

Hi Debbie, I'm not exactly sure what you mean by it is Microsoft behavior, the InstallShield application is not listing me drives on windows 8 that it did on Windows 7. Regardless of any "behavior issues", it needs fixing. Regards, /SiD ... View more

Thanks Michael. I've ended up doing the following, convoluted as it may be, it seems to work - just need to work out the update procedure now. 1) Create a basic MSI installer that has no UI, pre-requisites of VC11 runtime and .NET 4.0 client. This installs 2 files - the ones used by my suite to check for SQL server and allows them to be COM registered as they use .NET framework from the custom action DLL via interop. I include the suite and 2nd installer as additional files in the disk 1 folder. Final custom action of launching the suite installer with no wait. 2) Suite installer can now run with a UI and use the custom action DLLs, safe in knowledge that they are properly registered. Depending on what it finds, an option to install a "first machine" or "client machine" are offered with a button press to select. The different buttons set the different feature requirements in my suite which then controls whether or not to install SQL server before launching my main application install. I've added the billboards from the main installer to the progress screen in the suite as the main installer runs with no UI. Suite does not register itself in add/remove programs. 3) main installer runs silently with a command line parameter indicating if it was a "server" or "client" install. Simples!! So what i now have left is a) updates - i think i only need to worry about the main application at this point and can use FNC for this. b) Ideally i would like to uninstall the "Helper" installation that started this all off at the end of installation. Regards, /SiD ... View more

MichaelU wrote: Have you tried importing the prerequisite into your suite project? http://helpnet.flexerasoftware.com/installshield19helplib/helplibrary/SteImportPRQ.htm Hi Michael, Unless i am mistaken, the importing of the prerequisite will not help me as this is to associate with a feature/package I need the prerequisites to allow me to make a decision as to which feature/package is available and since the prerequisites are only installed when the "install" button is clicked, cannot do this. Regards, /SiD ... View more

Hi Michael, That's where i am at currently, i feel like i am groping in the dark trying to find out what i can and can't do with the suite. Just found the billboard control to add to my progress screen. Regards, /SiD ... View more

It did help a lot, once i had eventually tracked it down. I think it was the def file that made the difference. Regards, /SiD ... View more

Hi, can you provide some details as to how you have created your extension DLL, you say you got yours to work, How?? Regards, /SiD ... View more

Answering my own question, for the benefit of anyone running into the same problem, the action should read {SetProperty FEATURE[FirstMachine].actionState=install} not {SetProperty FEATURE[FirstMachine].actionState,install} ... View more