essexboy,
Just to be sure, yes I did this myself.
I changed my BETA Chrome version into the Development Build.
This was a test to change Chrome builds in the flight.
Thereby I hope, you saw there was on this system also a CANARY build of Chrome.
This was a test to run two Chrome builds together (DEV and Canary) and this was successfull.
So I want to have this also in the future.
On another Vista system running in triple mode on this same hardware I have also two Chrome builds together (Beta and Stable) and this runs also without problems.
The third system on this same hardware is a windows 10 system.
So our failing download w8.1 32bit system run together in triple boot mode with this Vista and Win10.
The also failing download W8.1 64bit production system runs on separate hardware and has only a stable chrome build running.
Further I must tell you that the failing download 8.1 32bit system for what you created the above FRST statements is already changed because of automatic update changes like the automatic Avast softwareupdater and the automatic updaters of Chrome, firefox and Windowsupdate.
Sorry, but because of testing also as much as possible is done automaticly there.
To solve the download problems on my 32bit 8.1 system I am ready to loose (temp) the 2 Chrome builds (Dev and Canary).
Now you know this, can I go on with the above FRST fixlist.txt or are you going to change something.
I am writing this on that Vista system and in an hour or so I am going to boot in my failing download 32bit 8.1 test system and will read you answer.
