sv.jgalloway
USA
Asked
— Edited
My son and I made our first bit of progress last night by getting our little bot up and going. But when we opened builder this morning, we noticed the "update available" tab flashing so we clicked on it. it took us to the download page which we did and everything went normally until we clicked on "finish" to exit the installer. The little hour glass icon appeared and didn't leave- for hours. finally, I restarted my computer, only to find that builder wouldn't open. Nothing unusual happens except it won't open, actually nothing at all happens.
Here's the Windows 7 .Net installer: https://www.microsoft.com/en-ca/download/details.aspx?id=42642
Also, there was an update to the ARC for another user. Maybe the new package will work for you? Try downloading it again and see if it helps.
Also, I re-installed builder. Still no go. The ARC icon is present and normal. I click on it, and nothing. It's almost like it's opening as normal, but the page doesn't come up. Like it does, when you open something to a screen that's minimized.
.net wouldn't install, because it said it was already installed on my computer.
I do not have another computer. I probably need to get a new one though, I've had this one for a few years now.
I would offer to do a remote TeamViewer session, but it will be several hours until I am free. Might want to try a Windows restore back to the last restore point. Something is clearly corrupted. Restore will fix any registry issues.
Alan
Alan
Alan
Alan
Jake just uploaded a diagnostic report. After thinking we had success last night, after a reboot the problem came back where ARC would not start. Task Manager showed three instances of ARC.exe running, but each only taking up 112k of memory. If we tried to start again, it could add three more tasks. The tasks could not be killed by task manager, killtask (run in a command prompt as administratot) or with sysinternals process explorer.
We rebooted, uninstalled, rebooted, re-installed and kept having the same issue. When we reverted back to the January 22nd version, it runs fine. However, it did have a problem connecting to the EZ-B until we added exclusions to Avast anti-virus. I am suspecting that may have been the issue with the newer version of ARC not running at all, but after spending a couple of hours, we decided to leave the old version for a week or so before tackling it again.
Do more recent releases attempt any network communication other than checking for update on bootup that the january 22nd version didn't do that might explain why Avast could be blocking it? If not, can you take a look at the diagnostic report and see if anything else jumps out at you that might prevent a newer version from working?
Alan