New
#1
Windows 7 resists repair by all means
A few months my new Acer Laptop worked well with windows 7 enterprise 64bit. One evening I had to shut it down by force, since it did not react any more to any input. Next morning windows started, but no application would be allowed to start, explanation was that the security rules would not allow that. Nothing helped, so I went back to a system restore point some days earlier and everything worked fine again. Some days later it started, but Firefox would not start. No other browser would either. When rebooting, windows would not start, windows own repair could not restore a working system. The problem details were:
=======================================
Problemereignisname: StartupRepairOffline
Problemsignatur 01: 6.1.7600.16385
Problemsignatur 02: 6.1.7600.16385
Problemsignatur 03: Unknown
Problemsignatur 04: -1
Problemsignatur 05: AutoFailover
Problemsignatur 06: -1
Problemsignatur 07: CorruptVolume
Betriebssystemversion: 6.1.7600.2.0.0.256.1
Gebietsschema-ID: 1031
=========================================
I still could and can get into the command line interface.
From this message I thought it might be some kind of harddisk problem. I ran chkdsk with /F and /R and I observed it finding some corrupted files. I was stupid enough not to save the names of them. Otherwise the hdd was ok. I interpreted the files as corrupted files through forced shutdown earlier. Nothing changed after that.
I thought about a hardware problem with the hdd. Using a Windows7PE CD I started the system, all partitions seemed to be okay and I was able to shift data back and forth. Unfortunately I could not get the Hitachi HDD-utility to check the drive but decided that being able to write and read large amounts of data should be convincing enough that the HDD was ok.
When trying to start in protected mode with CLI - the system hangs at CLASSPNP.SYS and reboots.
When trying to run sfc /scannow or /verifyonly I always am informed that there is still some system repair pending which would be closed at next boot. Needless to say the message always comes again after a new boot.
Is there still any more means to get the system working except a clean reinstallation which would wipe off everything I have done since the first installation? There are no important data on the machine but I am reluctant to invest time into tailoring it again. My latest backup is about 2,5 months old and I am not sure whether the restore process will work without problems.
In Windows XP there is the possibility to make a reinstall from the Windows-CD without ruining everything, but in Windows 7 this seems not to be possible any more from outside Windows.
Franz47