problem after update windows installer

Avast Free Antivirus / Premium Security
1

After the update of windows xp - windows installer the following problem arose:
If one the PC with Windows XP ton of drive down would like starts thesis again. If one places more of scriptblocker off with avast Prof. , then is this problem away.

regards Marko

2

I am afraid I really don’t understand what you are saying. What is your native language?

3

sorry , my language is german

4

the problem after updates of windows ( windows installer was updatetd )
the problem is: PC start again after switch off the PC
is more scriptblocker switched off, exists this problem not
best regards marko

5

OK, try to write the question in German please, I think I can understand that.

6

Nach dem Update von Windows XP auf mehreren PC´s ist folgendes Problem aufgetreten:
Der PC startet neu obwohl man den PC herunter fährt.
Schaltet man den Sciptblocker ab , so ist das Problem nicht da.

Danke Igor

7

Freely translated:
After updating XP (Microsoft Update), the system reboots itself when I select shutdown.
Turning off the scriptblocking in Avast will solve it.

Marko,
There is a known problem with one of the XP updates.
Microsoft has a fix for that in their knowledgebase.

(http://support.microsoft.com/?kbid=308029)

8

was kann ich dagegen tun ?
es gibt kein update dafür bei Microsoft
andere Virenscanner haben dieses Problem nicht
das problem liegt doch eindeutig bei avast prof. da nach dem abschalten des scriptblocker alles einwandfrei funktioniert

9

So, when you shutdown your computer, it only gets restarted. When you stop the Script Blocker before the shutdown, it powers off correctly. Right?
What is the exact build of avast! you have installed? There was an update a few days ago - the latest one is 4.6.763.

10

hallo Igor
ja ohne Scriptblocker funktioniert das Herunterfahren ohne Probleme.

Wir sind PC-Händler und avast-Reseller.
Es sind mehrere PC´s betroffen, alle sind neu installiert und die Windows Updates sind durchgeführt.
avast prof. ist mit der neuesten Version installiert ( 4.6.763 ) , Virendefinitionen sind geupdated, also auch auf dem neuesten Stand.

Best regards marko

11

I cannot image how Script Blocker could cause that…
Anyway, please try to disable the automatic restart, as desribed in the mentioned Microsoft Knowledgebase Article; maybe we will see that some error occurs.

12

Das ruft einen Bluescreen hervor, mit folgender Meldung:

STOP:C000021a {Schwerer Systemfehler}
Der Systemprozess Windows Logon Process wurde unerwartet beendet.
Status 0xc0000005 (0x00000000 0x00000000)
Das System wurde heruntergefahren.

13

Does this help?

14

Do you use Norton GoBack?

15

I was not sure but it is only XP related article about the error code “STOP:C000021a” I could find at Microsoft KB.

In my personal opinion, if everything O.K. without Script Blocker, it may be suitable for Marko to keep it turned off since the case seems to be special and that Script Blocker function is getting obsolete.

16

Ich habe kein Norton Goback installiert, es ist ein sauberes System ohne andere Programme die das verursachen könnten.
Es liegt nur an dem Scriptblocker.
Ohne Sciptblocker macht es jedoch keinen Sinn ein AVAST Pro zu installieren, es ist schade für die Firma alwil das sie keinen Support Ihren Händlern gegenüber geben können.
Da sollte sich schnellsten etwas ändern. das sage ich als Reseller von avast.

17

Loosely translated…

I didn’t install Norton Goback. It is a clean system and it is Script Blocker causing the problem. Without Script Blocker, it does not make much sense to install Avast! Pro version. As a reseller of Avast!, I have to say that it is sorry to see Alwil cannot support their dealer. This situation should be improved as soon as possible.

:-\

18

Well, you are the first one to have such a problem, nobody else ever reported this issue (and there certainly are many people running WinXP and Script Blocker) - so I’d tend to think the problem may be somewhere else (some kind of conflict with other tools running on those computers, for example).

Completely wrong. Since the introduction of Web Shield, the Script Blocker is mostly an obsolete feature - there is hardly anything Script Blocker would detect that Web Shield would not. There are more useful features in avast! Professional (Enhanced User Interface, Scheduler, Push updates) that are not present in avast! Home. Installing avast! Pro only because of Script Blocker is a nonsence.

If there is a bug in avast!, we would certainly like to fix it. However, if we cannot reproduce the problem (and we cannot - as I said, everything is working correctly elsewhere), it is rather hard to do.

Do the following, please:

  1. Send/post the list of running processes on the system (before shutdown)
  2. For every bluescreen, there should be a corresponding minidump file in C:\Windows\Minidump. Select a few recent files and send them to vlk@asw.cz.

Thanks.

19

As a happy Home user, it was difficult for me to defend Pro version and, of course, I am not complaining. ;D

However, seriously, as far as I know, marko, you seem to be an only person who has this problem, which is probably the reason why Eddy directed you to Microsoft KB for the first place.

20

Nach mehrmaligen Installationen und testen verschiedener Einstellungsvarianten sind wir auf des Rätsels Lösung gestoßen. ;D
Das beschriebene Problem mit dem Abstutz beim Herunterfahren des PC tritt nur bei den Systemen auf wo
das neueste Windows-Update installiert ist und die Desktopeinstellung auf “Klassisch” gestellt ist.
Wiederum tritt es nur dann auf, wenn das System mit einer Recovery-Installation installiert wurde, wobei es mehrere PC-Hersteller betrifft.
Die AVAST-Version ist dabei nicht ausschlaggebend.

Grüße Marko