Insite install issue

[Rawze]

This is just an FYI:
7.6.2 + its key%$maker, CT-3.17 + its key#%maker ... everything works just fine on win10. I saw someone install it not 2 weeks ago w latest win10 version. - No need to have such old hardware. I have also seen it running on win11, but that was many months ago.

If someone cannot get it running, then its simply that they do not know what they are doing.

One thing people do not realize is that the Sult#$ian key%$maker for 7.6.2 will fail with error to make key up to several dozens of times sometimes before it makes a legit key. - I saw it fail 40+ times in a row once, then make keys like a champ.

... and if your using the update manager, and it can see the internet at all ... even after everything is running ... everything will unregister (or try to update) your 7.6.2, CT, and everything else, ... as the update manager will every so often, dial home and defunct everything due to the red engine maker not being happy with what you have done. Update manager internet settings need to be set to 'Proxy' and IP address set to 127.0.0.1 for it not to dial home.

Couple things I noticed when watching someone else ...

== ALL anti-virus and defender softwares need to be fully disabled... permanently. This is not easy to do due to defender being very suborn to get fully switched off. CT and/or 7.6.2 gets crashes and startup errors if defender is not fully shut down.

== If ke$ymaker that comes with CT 3.17 ever reports that you have wrong version of CT ... then your PC has a virus on it that has attached itself to the CT executable, changing its MD5 signature. Here is how to check correct MD5 for those programs: https://rawze.com/forums/showthread.php?...6#pid64386

== NO special date locking software needed... But Date sync on PC needs to be turned OFF, and date also set on PC temporarily to before year 2020, before you even try to start installing 7.6.2. ... + NO INTERNET CONNECTION AT ALL until after install of everything + running once. - Date and Date sync can then be set back correctly + date sync turned back on after all is up and running though. Someone just needs to set the expiry (with keym$aker) date on 7.6.2 to like year 2057 or something during install.

related info:
https://rawze.com/forums/showthread.php?...9#pid68129

[ammjay61]

I did not know about the date sync. Good reading. Thank you, Sir!

[JimT]

Long story short, the missing runtime(s) needed to install Insite is the .NET 3.5 Runtime (It includes some older ones too) which you can get from MS like any other update.

Recently went through the install process on a brand new win10 pro installation and was running into the same initial problem with the installer failing almost right away. There were messages about a missing file, which wasn't actually missing. After a bit of research and fiddling around I figured out the installer expects an old .NET runtime to be present. .NET 3.5 runtime to be exact. The insite installer just expects it to be there and tries to use it without checking first, which is why the installer fails. While troubleshooting the insite installer I happened to install Meritor-Wabco Toolbox which also uses that runtime. But it checked first and windows prompted to download and install the .NET 3.5 Runtime (which required me to set the clock back to current year to validate). Once that was done Insite installed flawlessly, while following all the other instructions already mentioned.

Anyway, hopefully this helps others who have issues with the installer failing on win10 or 11. I've seen mention about win10 and 11 missing runtimes before, but no one ever identified which ones.

[tree98]

We'll see how long it works lol :)