Yet another 7.0.1473 failure, this time on XP x64

As others have noted there seems to be issues for many users when “upgrading” to 7.0.1473, in my case:

Win XP Pro x64
DEP Always On
Microsoft EMET
Spybot S&D (but only the browser immunisations, not normally running)
Comodo Firewall (only the firewall, no defence+ or AV)

As with everyone else, the install seemed to go well and I rebooted. The first indication that something was wrong was that there was no activity on my 3.5" FDD, normally I wait until it does a little rattle before clicking on my user account.

So I clicked on my user account and got my desktop background, but that’s all, no start menu, taskbar or icons. After leaving if for 5 minutes I tried the old Ctrl-Alt-Del and was able to get the task manager up and selected restart but that had no effect, after another 5 minutes I did a hard reset and booted into safe mode.

I was able to uninstall in safe mode, though that was needlessly difficult as the uninstall screen is to big for safe mode, rebooted and reinstalled 7.0.1466 and once again everything worked.

The WinXP 64bit is not exactly the best supported OS, mainly because nearly no one is using it due to awful support from software and drivers.

You do realise that’s not really an excuse, besides it’s happened to other OS versions.

Please reinstall without the behaviour shield…!!

Confirming that the behaviour shield seems to be the culprit, still I’ll stick with 7.0.1466 on my main machine.

OK, as you like.

I’ve face the same issue and completely-uninstall/freshly-reinstall 2 times.

The explorer.exe process doesn’t seem automatically start along with Windows itself. Therefore screen stay blank and empty after reboot. Bring on TaskMgr and manually run explorer process, then start menu, background and icons, ect… going well… but next time, user restart PC, it’ll happen again exactly same. So I uninstall the 7.0.1473 version.

So I’ve to unselect Behavior sheild in order to successfully install Avast 7.0.1473 and later (7.0.1474)?
Or 7.0.1474 already fix that, and I can install Avast newest version again without any missing sheild/features?

Sorry to dig this topic up, but I search around forum a few times, and this’s closest topic I saw. Thanks for reading and feel free relocate it to correct/suitable topic/thread if you feel necessary.

No issues on my computer. win xp sp3 32. Bit.
Any way did you have another antivirus on the computer before avast?. Most new computers come bundled with other antivirus on their restore recovery partitions/ cd restore disks.

All traces have to be removed using removal tools before using avast.

No issues on my computer. win xp sp3 [b][i]32. Bit[/i][/b]. Any way did you have another antivirus on the computer before avast?. Most new computers come bundled with other antivirus on their restore recovery partitions/ cd restore disks.

You sounds too hasty and uncareful at all. Ignore all the important info, just jump into the thread and throw something like that, while still thinking you’re actually help anothers?
I’ve setup and update Avast to 7.0.1473/1474 in both Win7 32bit/64bit and XP 32bit without any problem. Just one PC Windows XP 64bit SP2 hit that problem.

A keyword here is 64-bit, man. And it’s official confirmed in this forum, by a guy from Avast team:

Yes, it’s already fixed in 7.0.1474.