My version of FrmWrkLib.dll is 2.0.0.347 so I think I'm up to date. Would a copy of my .isl and .isproj files be helpful? Can I remove the component by editing .isl file directly? There appear to many references to the dll I wish to remove (Delimon.Win32.IO.dll) as shown below: Search "Delimon" (13 hits in 1 file) C:\Users\Simon\Documents\Visual Studio 2013\Projects\SetTags\SetTags\SetTagsInstall\SetTagsInstall.isl (13 hits) Line 344: Delimon.Win32.IO.dll{7A871BF2-87B2-4363-BB2A-8A501C3C15E5}SETTAGS12delimon.win32.io.dll17/LogFile=/LogFile=/LogFile=/LogFile= Line 344: Delimon.Win32.IO.dll{7A871BF2-87B2-4363-BB2A-8A501C3C15E5}SETTAGS12delimon.win32.io.dll17/LogFile=/LogFile=/LogFile=/LogFile= Line 1064: INSTALLDIRDelimon.Win32.IO.dll Line 1075: SETTAGS1Delimon.Win32.IO.dll Line 1901: AlwaysInstallDelimon.Win32.IO.dll Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 1926: delimon.win32.io.dllDelimon.Win32.IO.dllDELIMO~1.DLL|Delimon.Win32.IO.dll001C:\Program Files (x86)\Delimon\Delimon.Win32.IO\Delimon.Win32.IO.dll1 Line 2080: Delimon.Win32.IO.dll_3A4993F8_E5E6_447E_BA83_94A83ACE23BB_FILTER Line 2631: delimon.win32.io.dll1 ... View more

After trying all the suggested fixes in KB article (reinstalling InstallShield LE, checking for missing files specified in application files, files with commas in name, repairing VS 2013 (on which I was getting Error -6109 on build for my project) I eventually found I could select all the Application Files from the Program Assistant Application Files screen, right-click and then set Scan at Build to None. This allowed the build to proceed without error. A project which had previously built OK also failed - haven't tried resetting the Scan at build values for it yet, so I don't know what change caused InstallShield LE to start throwing the error. Repairing VS 2013 (running on Win 10) was problematic - needed to turn off Malwarebytes malware protection to avoid a hang and then got prompted for some missing msi files which I was able to download. I had uninstalled .Net 4.5 which crippled Visual Studio and downloading and trying to install .Net4.5.1 failed as it said it was already installed (Win 10 uses .Net 4.6.2). Fortunately the repair of VS2013 reinstalled .Net 4.5.1 but Netver executable still says its not installed. .Net 4.5.1 appears now in Programs and Features list. Postscript: after changing Scan at Build to None, all files required have to be manually added in the Application Files Window. If any aren't present the installer may complete successfully on a target machine but then crash on execution, sometimes with only a crashdump file to indicate what was wrong. I can't find any application which performs the scanning function to detect dependencies and thus needed files and I've had to work from the files packaged before InstallShield LE manifested this bug. ... View more