One more reason can be there for the ISDEV : error -7132: An error occurred streaming ISSetup.dll support file ..\Release..\Setup.inx. If you mistakenly deleted the 'Script Files' folder or contents inside it, The same error will occur.
If there is a syntax error you should normally have a -4370 build error indicating that there were errors compiling InstallScript. The specific cause of the compilation error should also be found in the log file.
Unfortunately, what makes DLL files so convenient and efficient, also makes them extremely vulnerable to problems. If something happens to a shared DLL file, either it goes missing or gets corrupted in some way, it can generate a "runtime" error message. Runtime is pretty self-explanatory; it means that these errors are triggered when ISSetup.dll is attempted to be loaded either when Realtek High Definition Audio Codec (Windows 7 / 8/ 8.1/ 10 64-bit) is starting up, or in some cases already running. Some of the most common ISSetup.dll errors include:
The setup prerequisites concept only allow you to analyze the registry or files to determine if a 3rd party setup should be run. What you are looking for is to run a Custom Action very early in the UI sequence that will check if IIS Admin Service is running, then set a condition code or error message that will alter processing. The Custom Action could be InstallScript or VBScript to accomplish this. 2b1af7f3a8