February 4, 20188 yr I am receiving this error when launching wrobot as well as when launching other dialogues. This will occasionally cause me to crash. I have done .net Framework repair and made sure I have the newest C++ redistributable. Any suggestions?
February 7, 20188 yr Author Tried doing it on hard drive and not flash drive, same error with fresh install.
February 8, 20188 yr Author Yes, I have done the entire Repair/Install list. And the servers yesterday would give a bad login error but that is fixed today. Looks like null01 is in the same boat?
February 8, 20188 yr Author Log has nothing before actually launching bot. I will note, this only happens once per restart of computer. If I close bot, and re-open, there is no error.
February 8, 20188 yr it seems the application isn't using the net framework properly which could be the application side if it's going in & out or I am way out of the ballpark when googling around about the Win32Exception (0x80004005) 1. What versions of Microsoft .NET Framework is installed Microsoft .NET Framework 4.6 should be installed and 3.5 comes default with windows 10 My suggestion is to uninstall all existing .NET Frameworks from the system, including uninstalling .NET Framework 3.5 from Windows Features. Steps are: Press Windows key + R Type: optionalfeatures.exe Hit enter Uncheck .NET Framework 3.5 (includes .NET 2.0 and 3.0) checkbox and any other windows net framework, select OK, and reboot your computer if prompted. (this is what net frameworks I have installed atm on windows 10) Once rebooted make sure .NET Framework 3.5 is installed first. Press Windows key + R type: optionalfeatures.exe Hit enter Select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box, select OK, and reboot your computer if prompted. Then install .NET Framework 4.6 (Web Installer) If it is still having problems after that, then try NET Framework Repair Tool. If issue still exists let me know ill try to help further anyway I can
February 8, 20188 yr Author Thanks, that fixed it. I didn't have to re-install anything but just disabling .Net + restart, enabling + restart fixed it. :)
Create an account or sign in to comment