OK - BUT… any NEXT reboot (after first that does finalization of installation) will revert to original aswTdi.sys file, which is bad.
So we are only doing a test-drive to se if also on my computer, with patched aswTdi.sys all works fine - i.e. if it not hangs, yes?
After all I will have to uninstall again avast! and keep the system clean of it until you release new update with corrected aswTdi.sys. Because after next reboot (no matter if I do it in next half hour or two days) will start avast! with originalaswTdi.sys and the system once again begin to hang-up with BSOD after a few minutes from rebooting.
So we are only doing a test-drive to se if also on my computer, with patched aswTdi.sys all works fine - i.e. if it not hangs, yes?
Exactly.
After all I will have to uninstall again avast! and keep the system clean of it until you release new update with _corrected_ aswTdi.sys. Because after next reboot (no matter if I do it in next half hour or two days) will start avast! with *original*aswTdi.sys and the system once again begin to hang-up with BSOD after a few minutes from rebooting.
That’s right. But if the driver proves to work we’ll issue the update soon (before the end of weekend).
Works now for 35 minutes after reboot done for finalizing instalation. Before reboot I’ve patched aswTdi.sys with a new file. No BSOD, no change, no strange behavior - all seems to be OK.
Or maybe not all OK. You said that it will try to revert this file to original and ask to reboot, which I should not do. Nothing happent like that. I’m monitoring C:\WINDOWS\system32\drivers on my XP HE SP2 for all 35 minutes and the file was not change - so the reboot was not called to be necessary. Strange. I did NOT change anything in avast! It runs like it was installed.
The file was not reverted so it is safe (in my opinion) to reboot / turn off computer and using this new (4.5) patched version as it should not crash the system after next run. If it does, I will report you.
pk!: You wrote that first time you published the patched file, it was still bad and we have to download it again. Well I’ve downloaded it twice - before and after your message, and BOTH times it was the same file - 28 672 bytes long. After installing new avast! 4.5 the file was 32k long but after patching it, it still stays at 28,672. avast! does not tried to revert it to original 32k up after now.
Vlk: I’m going to sleep now. My computer is going to sleep too. But avast! never asleeps! When I find anything else tommorow or next day I will report this to this forum.
Thanks for all help and good look. Have a peaceful night! Regards!
Tom
There was only one fixed version we published. Unfortunately, nimrod666’s new aswTdi was replaced from backup with the problematic file - that’s why he wrote that nothing changed in his 2nd post. Good night ;).
Ran computer today for around 3 hours. There were several reboots and working on both accounts I have on my XP. There were no problems. avast! did not update aswTdi.sys at any time up until now and did not ask for rebooting. There was no BSOD any more as up to now.
P.S.: I’ve installed an old program today that also installed Microsoft Virtual Machine with it. Which SP2 automaticly updated from Windows Update. But it cause no change in system’s or avast!'s working. I don’t know if Ms VM have any influence on avast! Just wanted to inform you about it.
- for quick checking.
