Whilst awaiting a response I tried burning the win7-32bit rc.iso using ImgBurn on my XP Pro system which has an optical drive and ImgBurn is only listing my optical drive and the drop down list doesn’t show any other devices (my USB stick).
So currently ImgBurn is incapable of burning the ico to the USB.
All of which may well be moot if the netbook hard drive is toast.
Well I ran rufus OK and used another burner app, Passcape ISO Burner at first it wanted to over write the contents of the USB and I allowed it to do that. This appeared to be somewhat lacking after running it, so I ran rufus again and then this tool again but with another option to unpack the contents of the iso to the usb drive.
See images of the main root directory and the sources sub-directory, I don’t know if this is what it would look like or not. I haven’t copied the FRST.exe file to the root directory yet, I though I would wait for confirmation.
This said, this is looking more like a hardware failure than anything else right now:
Drive activity light doesn’t come on.
Can’t tell if it is just the led (unlikely) as I cant tell if the noise I can hear is the fan or drive.
Having closed the lid, that is meant to put the system into sleep mode. Though the power light is Blue and not Orange as it should be if it were in sleep.
Now I guess most of these (2&3) could be related to the system not booting, number 1 should see some drive activity as it tries to boot, so the jury is still out.
I don’t know if the default settings in the BIOS allow for a USB boot and I can’t access them to even check.
Given your note:
Insert the USB into the sick computer and start the computer. First ensuring that the system is set to boot from USB
Note: If you are not sure how to do that follow the instructions Here
I haven’t copied over FRST.exe, but that is a few seconds and has now been done.
So I will just boot with it in and see if there any response.
Well good news of a sort, win7 is up and running again, but it wasn’t the bootable USB or FRST that did it.
Having said that I will just shutdown plug in the USB and see what happens. Well there was a little activity flash on my screen followed by the ‘Your system didn’t shutdown correctly’ or words to that effect, I chose to boot into safe mode with networking.
When I got in I did a windows Run wusa.exe /uninstall /kb:2823324 /quiet /norestart as mentioned in an article Bob posted the link to http://www.zdnet.com/microsoft-pulls-patch-tuesday-security-fix-7000013942/ and left it for a little while. I then did a restart and windows said it was still updating and when complete rebooted.
On the restart I got the usual finalising an update screen and finally Logged on. So fingers crossed this was that bad KB and that the removal command did the trick.
So that command did do the trick from what I’m reading.
Now I’m wondering how many of the Avast customers running Windows 7
are blaming Avast for Microsofts mistake ???
How can we figure out if this is an avast! problem on a Windows 7 system or a
Windows update that screwed up their OS ???
I guess having the customer check if they have kb:2823324 installed would be one bit of needed information if the problem
on the Win 7 system started shortly after a windows update
It would appear so and certainly MS have been pretty quiet about this one, well the reasons behind it only reporting the error number and ID. But it appears that this issue is with 3rd party applications and more so 3rd party security based applications.
So yes it is possible this could be unknowingly effecting avast users and they would naturally blame avast, no one thinks about hang on this only happened after a windows update.