Launcher caught in endless Build 0 loop

Support
1

I’ve been messing with this for a while tonight, trying to find a sequence that will work. So far no luck.

Below is what I’ve done so far, each of which has the same result of showing Current Build: 0, New Build: 199

Win7 x64, ~60GB free drive space

Allowed Launcher to download update
Ran Automation Cleaner, re ran launcher, launcher downloaded Build 199
Ran Automation Cleaner, manually downloaded launcher and Build 199, C:\ProgramData\Automation folder 839 MB in size
Ran Automation Cleaner, deleted C:\ProgramData\Automation folder, deleted documents\Automation folder, ran manually downloaded launcher & build
Reset permissions on ProgramData\Automation folder giving my account full control of the folder and all subfolders/files
Created new user account on machine, tried the above steps again

So at this point pretty much out of ideas, anybody have anything else to try?

2

Mine installed cleanly must be something in your set up…

3

Reinstall the launcher, or have you moved the launcher away from the ProgramData\Automation folder?

Either way, it sounds like the Launcher is not in the same folder as where the installer is going to.

4

Re installed the launcher, Automation Launcher.exe currently sitting in ProgramData\Automation. Ran it directly from that folder & same result.

5

Now that is bizarre. The launcher is version 43? You do get asked to let this program make changes to your computer (if you are on vista/7/8?)

In the program data folder, you also see an Automation.dll?

6

Yep, launcher is at version 43, I’m getting the UAC prompt to allow access, Automation.dll is present, don’t see a version on it but its 1.03 MB.

7

Hi Ducks, can you download the run the Automation Cleaner from here: viewtopic.php?f=16&t=1271

Then go into ProgramData\Automation and make sure only Automation_Launcher and Uninstall.exe remain.

Then install the full installer B199 again.

This is all very odd, the only reason it will be getting stuck in a 0 update loop, is if it cannot read the Automation.dll. This can only happen in a couple of ways, the short cut to the launcher is message up, and the launcher runs looking at a different folder for automation (running it directly from the folder gets around that). Or the Automation.dll or the checksum file are corrupt.

8

Ran the cleaner, only those two files remained, reran the 199 setup & ran the launcher form the programdata folder, same result unfortunately. The MD5 checksum on the Automation.dll is C225B3A957316350FC658185D8F20107 if it helps any.

Thanks for the help so far.

9

Finally figured out my problem, to give a little background I’m a sysadmin working in security by trade and run a windows domain at my house, I had the following group policy setting enabled “System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing algorithms”, disabling that fixed my problem. My assumption is if your launcher is trying to compute the hash of the content it downloaded its silently failing because windows was not allowing a hash to be calculated. 99.9999999999999999% of home users would never have this setting enabled but I figured I’d post my solution in case somebody else ran into the same problem.

Now off to make some massive boost!

10

Wow, that is boutique issue. The launcher runs some MD5 checksums of various files, so that makes sense.