I am just now learning how special the %windir%\system32 folder is, not just on Windows 7 but even worse on Windows 10. Currently the build process I am using to create install kits is running on build machines that are based on Windows 7.  Since Windows 10 functions differently, I am wondering if perhaps I will have almost insurmountable issues when that install kit is targeted for a different OS version, specifically Windows 10. ... View more

I am using basically the general design for an installation kit on Windows 7 and Windows 10.  I am using InstallShield 2018 (not R2), as that is what I have current licenses to use.  Correct me if I am wrong, but for our multiple builds machines we would have to pay to upgrade to R2, right? On Windows 7 I have enough issues to deal with, but at least when I uninstall or upgrade I can get old files to be removed from the System64Folder.  On Windows 10, however, all attempts to replace or remove those files have failed. One of the things that I have tried is to use a custom function, shown here: //--------------------------------------------------------------------------- function void DeleteInstalledFile(szFolder, szFilename)      // Delete the file from the specified folder and log the results.      STRING svResult; begin      if (DeleteFile (szFolder ^ szFilename) == 0) then          SprintfMsiLog("###> DeleteInstalledFile: %s\%s deleted", szFolder, szFilename);      else          DeleteFile(TempFolder ^ szFilename); // Make sure rename destination is removed           if (RenameFile(szFolder ^ szFilename, TempFolder ^ szFilename) == 0) then               SprintfMsiLog("###> DeleteInstalledFile: %s\%s renamed %s\%s",                  szFolder, szFilename, TempFolder, szFilename);               BATCH_INSTALL = TRUE;           else               if (FindFile(szFolder, szFilename, svResult) != 0) then                   SprintfMsiLog("###> DeleteInstalledFile: cannot find %s\%s", szFolder, szFilename);               else                   SprintfMsiLog("###> DeleteInstalledFile: cannot rename %s\%s", szFolder, szFilename);               endif;           endif;      endif; end; The DeleteFile operation fails.  Then the RenameFile operation fails.  Even the FindFile operation fails.  And yet the file persists. I have the Required Execution Level set to Administrator. Using a command shell launched as administrator I can clean up these things manually.  But of course I cannot ask our customers to use a batch script to make up for what the install kit will not do. ... View more