Windows 7 Home Premium: Repair Install fails with error

RxyzM · 20 Nov 2017

Hello,

I am facing issue in doing Windows 7 Home premium repair install.

Microsoft help desk already asked me to reformat the drive and re-install the windows. Don't want to do that because I do not want to lose current S/W setups and accounts that have been created on this machine from last 4/ 5 years.

Briefly:

======================

The issue started when I shutdown the machine using Windows shutdown function on a Saturday evening and when I switched machine back on Sunday, the desktop icons had shrunk; the icon labels were unreasonably small (almost microscopic). USB Mouse had stopped responding. The icons on the initial account screens were had also shrunk to some extent and the text was unreadable.

In my experience this is usually the case that indicates corruption of windows fonts. However, could not find and problem there.

However, when booting machine on Sunday, the startup informed that I should run CHKDSK. I tried running that, but it failed and kept failing. I then used windows original CD to start the repair mode and from the option there, somehow CHKDSK completed it's run and the system booted.

I then created a boot CD. Using that, I booted machine into DOS prompt and tried registry restoration operation from registry backups. To do that, I created backup of current Registry state by copying the current registry files on to a separate disk. I tried this since the system restore could not find any restore points. This is surprising, since windows is supposed to create automatic restore points whenever a major installation happens and in my case, I had installed S/Ws such as Anti-virus... Oh, well, so much for expectation.

Since the registry restoration did not fix the issues, I restored registries from current registry backup files and booted the machine. No issues were resolved till this time. I then went into device manager and deleted USB port entries. I let the system rebuild USB maps while booting. This at least solved the USB response issue for all USB ports.

======================

But, the machine is still not back to it's original state. The icons are a bit ok, but, the fonts are still very small (unreadable).

Have tried to run SFC under different authorities including Admin. It always fails with "Windows Resource Protection could not start the repair service" error. Have ensured again and again that the related service is ON when SFC is executed.

Now I am trying the Windows Repair Install option. It kept failing with "Your windows version is current than....". So, went through some forums and found that I need to have Windows 7 Home premium with SP1 (ID: XT-58996.iso) ISO. Got that from Microsoft site in a roundabout way. Got it expanded on a DVD and made it as bootable disk.

Now when I run Repair Install, it completes the compatibility check, but, fails in gathering system settings step. No error is shown except, windows has encountered an issue and therefore, the marked changes have been rolled back. The repair install aborts and I am back to square one.

Repair Install also informs me that the COM2 and LPT1 ports require driver upgrades. Also, that I should uninstall iTune (what is deauthorize? The error tells me that I need to deauthorize this program); Autocad 2007, Microsoft XP Power tools.

However, in the list of installed programs, I do not see iTune installed. Autocad, when tried to uninstall, points to E drive which is my DVD drive and because of that can not uninstall it.

======================

Today, with Microsoft help desk, during the debug session established with them, the help desk person re-installed the VGA driver for ASUS board (my Mother Board is from ASUS with AMD processor). Situation of the display has remained same with the Screen images of icons and label text.

SFC still can't be run; still fails with Windows Resource Protection could not start the repair service". for this when I checked with Microsoft technical support member. He advised me to run DISM, but, I am not sure whether DISM is available in Windows 7 home premium.

======================

Will really appreciate any help, pointers to have my issues resolved.

Warm Regards,

Ravi

torchwood · 20 Nov 2017

Hi RxyzM,

MS should have asked you to run SURT 32bit, link attached,
Download System Update Readiness Tool for Windows 7 (KB947821) [October 2014] from Official Microsoft Download Center

DISM doesnt cover W7 in your case

Depending on what it finds could take a while to run, copy/paste the output.

Roy

Megahertz07 · 20 Nov 2017

Welcome to the Forum

Please edit your profile with ALL your hardware specs.

I suspect you have a disk issue.
Boot from the Win 7 installation disk, go to repair and launch a CMD window. Type
chkdsk c: /f
Pay attention on the results, specially bad blocks and / or bad clusters.

If no errors found, type
sfc /scannow

RxyzM · 21 Nov 2017

Thank you Roy, Megahertz07. Really appreciate your inputs.

I will work with them at the earliest (normally, I am working with my issues on Saturday/Sunday). Will post the results here at the earliest.

Warm Regards,

Ravi

RxyzM · 25 Nov 2017

Hi Roy,

here is the output - Checksur.log, bcdedit data, for CheckSUR and bcdedit tools respectively, from my machine.

I believe to perform repairs, CheckSUR tool is looking for d:\win7sp1_gdr..... directory path. I checked on my machine and there is no such directory on D drive.

But, I use Bitdefender as AV and it has protected some files in C drive. This AV protects OS files from being replaced unauthorized. However, I am not sure how to rescue these files. Since this corruption, bitdefender in my machine has stopped working.

One point that I am not able to figure out is when start CMD, it starts with D:\Easy... directory. Normally, the CMD should start in User's default directory in C: drive. So, there is something changed.

Code:

=========

BCDEDIT Data

identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {f98e95d1-bd1e-11df-a252-89b8e2ac6564}
displayorder            {current}
toolsdisplayorder       {bdbdbd00-6057-11e0-a7f3-ce9adfd72003}
                        {bdbdbd00-6057-11e0-a7f3-ce9adfd72002}
                        {bdbdbd00-6057-11e0-a7f3-ce9adfd72001}
                        {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {39b9ce87-3a57-11e1-bf10-a87b52e8cf79}
device                  ramdisk=[C:]\Recovery\f98e95cf-bd1e-11df-a252-89b8e2ac6564\Winre.wim,{39b9ce88-3a57-11e1-bf10-a87b52e8cf79}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered) 
locale                  
osdevice                ramdisk=[C:]\Recovery\f98e95cf-bd1e-11df-a252-89b8e2ac6564\Winre.wim,{39b9ce88-3a57-11e1-bf10-a87b52e8cf79}
systemroot              \windows
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {a4278cb3-79e2-11de-ab5d-bf7a2caabdc6}
device                  unknown
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoveryenabled         Yes
osdevice                unknown
systemroot              \Windows
resumeobject            {a4278cb4-79e2-11de-ab5d-bf7a2caabdc6}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {f98e95cd-bd1e-11df-a252-89b8e2ac6564}

Windows Boot Loader
-------------------
identifier              {f98e95cf-bd1e-11df-a252-89b8e2ac6564}

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {f98e95d5-bd1e-11df-a252-89b8e2ac6564}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {f98e95d1-bd1e-11df-a252-89b8e2ac6564}
nx                      OptOut

Windows Boot Loader
-------------------
identifier              {f98e95d5-bd1e-11df-a252-89b8e2ac6564}

Resume from Hibernate
---------------------
identifier              {a4278cb4-79e2-11de-ab5d-bf7a2caabdc6}
device                  unknown
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              unknown
filepath                \hiberfil.sys
pae                     Yes
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {f98e95d1-bd1e-11df-a252-89b8e2ac6564}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
pae                     Yes
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

Windows Legacy OS Loader
------------------------
identifier              {ntldr}
device                  unknown
path                    \ntldr
description             Earlier Version of Windows

Real-mode Boot Sector
---------------------
identifier              {bdbdbd00-6057-11e0-a7f3-ce9adfd72001}
device                  partition=C:
path                    \bdr-ld01.mbr
description             Bitdefender Rescue Mode - Windows 7 Home Premium SP 1 (x86)

Real-mode Boot Sector
---------------------
identifier              {bdbdbd00-6057-11e0-a7f3-ce9adfd72002}
device                  partition=C:
path                    \bdr-ld02.mbr
description             Bitdefender Rescue Mode - Windows 7 Home Premium SP 1 (x86) 2

Real-mode Boot Sector
---------------------
identifier              {bdbdbd00-6057-11e0-a7f3-ce9adfd72003}
device                  partition=C:
path                    \bdr-ld03.mbr
description             Bitdefender Rescue Mode - Windows 7 Home Premium SP 1 (x86) 3

Real-mode Boot Sector
---------------------
identifier              {d2b69194-8f14-11da-a31f-ea816ab185e9}
device                  partition=C:
path                    \ESLOADLX
description             EaseUS Todo Backup Linux

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {39b9ce88-3a57-11e1-bf10-a87b52e8cf79}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\f98e95cf-bd1e-11df-a252-89b8e2ac6564\boot.sdi

Device options
--------------
identifier              {f98e95ce-bd1e-11df-a252-89b8e2ac6564}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\f98e95ca-bd1e-11df-a252-89b8e2ac6564\boot.sdi

Device options
--------------
identifier              {f98e95d0-bd1e-11df-a252-89b8e2ac6564}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\f98e95cf-bd1e-11df-a252-89b8e2ac6564\boot.sdi

Device options
--------------
identifier              {f98e95d6-bd1e-11df-a252-89b8e2ac6564}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\f98e95d5-bd1e-11df-a252-89b8e2ac6564\boot.sdi


=========

CheckSUR Log

=========

With Warm Regards,

Ravi

RxyzM · 25 Nov 2017

Megahertz07 said:

Welcome to the Forum

Please edit your profile with ALL your hardware specs.

I suspect you have a disk issue.
Boot from the Win 7 installation disk, go to repair and launch a CMD window. Type
chkdsk c: /f
Pay attention on the results, specially bad blocks and / or bad clusters.

If no errors found, type
sfc /scannow

Hello Megahertz07

I have attached a word document here that contains the log output for CHKDSK. It ran fine; did not show any error, however SFC /SCANnow fails with "Windows Resource Protection could not start the repair service" error.

I am not able to locate the SFC Log in case that is available somewhere. Could it be in Event Log?

With Warm Regards,

Ravi

torchwood · 25 Nov 2017

Hi Rxyzm,

there appears to be massive corruption on your system.
not surprised MS couldnt fixit on line
(see SURT log - you are missing not only update manifests but system ones as well)

I can provide certain missing files but not all of them, the Sysnative forum will have them:).
It would actually be a lot quicker to perform a clean install,
As you dont want todo this i suggest you shoot over to Sysnative
They will require the logs from post#5 and the results of thier own tool
http://www.sysnative.com/niemiro/apps/SFCFix.exe
keep it on your desktop
They may also request you use this tool as well, FRST
Downloading Farbar Recovery Scan Tool

they get busy be patient, and the fixs could take a while, its certainly not a one hit job.

Roy

RxyzM · 25 Nov 2017

torchwood said:

Hi Rxyzm,

there appears to be massive corruption on your system.
not surprised MS couldnt fixit on line
(see SURT log - you are missing not only update manifests but system ones as well)

I can provide certain missing files but not all of them, the Sysnative forum will have them.
It would actually be a lot quicker to perform a clean install

checking be right back

Hi Torchwood,

Thank you for your kind help.

I was suspecting System corruption, but not to this extent. However, I also have setup lot of s/w on this machine. At home, this is a common machine used for multiple purposes.

Do not want to lose all the setups and hence trying to work with this tough way.

Let me know which files that should look for on Sysnative forum. Also, once I get the files, how do I get them included for CheckSUR to find and work with?

Warm Regards,

Ravi

torchwood · 25 Nov 2017

Hi Ravi,

Sysnative is a forum that specialises in Windows Updates and OS corruption, they have a vast library of files

One of thier people will guide you thru the process and provide the missing files and tell you how to input them, using the 2 tools i mentioned, (sfcfix and FRST).

NOTE
i have amended my previous post please re read it, i updated it after doing some checking.

Roy

RxyzM · 25 Nov 2017

Thank you Roy. I will do as you have suggested.

I am sure this will not be a one hit job. I have been struggling with this for last one month or so. Initially, it was difficult to even get the USB mouse and Key board working. Had to get new keyboard with PS/2 connector because only that was working on this machine as input device.

Warm Regards,

Ravi