@igor
I never said it was a prescription to anything - merely that I had what was said to not exist, and posted the steps by which I came across it in case anyone else wanted to see what they could see with it. I even posted several warnings about using that method, and that it would be better to stay with 7.0.1474 as opposed to forcing the version that I had for those that wanted to stay with ver. 7 for now.
I'm not sure if you're implying that I'm attempting to make people damage their systems, but review of my posts would show that's clearly not the case.
Upon further inspection, if you attempt to search for version updates manually (since the system shows that 7.0.1483 is up to date), it will skip straight to step 3/3 and install ver. 8. As such, it doesn't seem to break the program at all in respect to updating - it will follow the standard progression from 7.0.1474 to 8.0.1483 if allowed to do so.
Running a system scan with 7.0.1483 shows no errors. This was found to be the case on two systems.
Running a system scan with 7.0.1483 later allowed to update to 8.0.1483 shows no errors. This was only tested on one system thus far.
Running a system scan with 7.0.1474 updated directly to 8.0.1483 in a standard manner resulted in several flagged Avast files. This was tested on a system that never had Avast installed, so there could be no conflict from a previous installation. I'll be testing a direct installation of 8.0.1483 to see if that resolves the issue.
EDIT:
I've since run a check for corrupted files and found none on the systems that had an interrupted update, then progressed to 8.0.1483. I've also added in the optional modules and run another system scan - no errors.
However, as with the system that had a standard install/update, the Software Updater and Browser Cleanup are both having issues:
- Browser Cleanup keeps insisting that I need to close Explorer to continue, but Explorer is not open
- Software Updater endlessly prepares to check for updates for Java