Windows 7 Home Premium: Repair Install fails with error

[RxyzM]

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]

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]

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]

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]

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.

=========

[U]BCDEDIT Data[/U]

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

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

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

Windows Boot Loader
-------------------
identifier              [COLOR="yellowgreen"]{f98e95cd-bd1e-11df-a252-89b8e2ac6564}[/COLOR]

Windows Boot Loader
-------------------
identifier              [COLOR="yellowgreen"]{f98e95cf-bd1e-11df-a252-89b8e2ac6564}[/COLOR]

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

Windows Boot Loader
-------------------
identifier              [COLOR="YellowGreen"]{f98e95d5-bd1e-11df-a252-89b8e2ac6564}[/COLOR]

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

Resume from Hibernate
---------------------
identifier              [COLOR="YellowGreen"]{f98e95d1-bd1e-11df-a252-89b8e2ac6564}[/COLOR]
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              [COLOR="DarkOrange"]{bdbdbd00-6057-11e0-a7f3-ce9adfd72001}[/COLOR]
device                  partition=C:
path                    \bdr-ld01.mbr
description             Bitdefender Rescue Mode - Windows 7 Home Premium SP 1 (x86)

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

Real-mode Boot Sector
---------------------
identifier              [COLOR="darkorange"]{bdbdbd00-6057-11e0-a7f3-ce9adfd72003}[/COLOR]
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              [COLOR="MediumTurquoise"]{39b9ce88-3a57-11e1-bf10-a87b52e8cf79[/COLOR]}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\[COLOR="YellowGreen"]f98e95cf-bd1e-11df-a252-89b8e2ac6564[/COLOR]\boot.sdi

Device options
--------------
identifier              [COLOR="YellowGreen"]{f98e95ce-bd1e-11df-a252-89b8e2ac6564}[/COLOR]
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\[COLOR="yellowgreen"]f98e95ca-bd1e-11df-a252-89b8e2ac6564[/COLOR]\boot.sdi

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

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


=========

[U]CheckSUR Log[/U]

=========

With Warm Regards,

Ravi

 

[RxyzM]

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]

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]

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]

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]

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. :shock:

Warm Regards,

Ravi

 

[RxyzM]

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

Hi Roy,

One thing I noticed is -

For windows directory in C: drive, following is ACL setup

C:\>cacls windows
C:\Windows NT SERVICE\TrustedInstaller:F
NT SERVICE\TrustedInstallerCI)(IO)F
NT AUTHORITY\SYSTEM:C
NT AUTHORITY\SYSTEMOI)(CI)(IO)F
BUILTIN\Administrators:C
BUILTIN\AdministratorsOI)(CI)(IO)F
BUILTIN\Users:R
BUILTIN\UsersOI)(CI)(IO)(special access
GENERIC_READ
GENERIC_EXECUTE

CREATOR OWNEROI)(CI)(IO)F

But for winsxs directory, the acl setup is -

C:\Windows>cacls winsxs
C:\Windows\winsxs NT SERVICE\TrustedInstallerOI)(CI)F
BUILTIN\AdministratorsOI)(CI)R
NT AUTHORITY\SYSTEMOI)(CI)R
BUILTIN\UsersOI)(CI)R

I came across a note on another forum, where the SFC was failing (with the same error that I was getting) because the Administrator did not have right access for winsxs and PendingDeletes and PendingRenames directories in winsxs.

Do you know, in general what should be standard ACLs for these directories?

Warm Regards,

Ravi

 

[torchwood]

Hi Ravi,

not really into permissions so cant say for sure,
However the 2 tools i mentioned both use top level permissions, and if they are blocked whilst they try to perform the corrections the Sysnative helper will also be able to correct them as well.
quick guide link
Reset All User Permissions To Default - Tips and Tricks

Once you have moved over to them please DO NOT make any other changes, follow thier instructions to the letter, to many cooks is not a good idea They are the experts

REALLY IMPORTANT
Once the problems are sorted create an Image, it will save you a lot of time and grief
most here use macrium free


Roy

 

[RxyzM]

Hi Ravi,

not really into permissions so cant say for sure,
However the 2 tools i mentioned both use top level permissions, and if they are blocked whilst they try to perform the corrections the Sysnative helper will also be able to correct them as well.
quick guide link
Reset All User Permissions To Default - Tips and Tricks

Once you have moved over to them please DO NOT make any other changes, follow thier instructions to the letter, to many cooks is not a good idea They are the experts

REALLY IMPORTANT
Once the problems are sorted create an Image, it will save you a lot of time and grief
most here use macrium free


Roy

Hi Roy,

Thank you for your inputs and suggestion.

Will certainly create an image after the issue is fixed. I can't even say a valuable lesson learned. Have spent 30+ yrs. in IT :huh:

Warm Regards,

Ravi

 

[Megahertz07]

Normally a big corruption like you had is due a power failure or a dying disk. Check disk says your disk is good. So what caused the corruption?
You're trying to fix a windows installation, but you don't know what was the failing reason.
Do you have your data backed up?

You didn't gave us all the hardware specs (I asked on post #3)
I would put your disk on another desktop and do a disk image. If something goes wrong you can have have it back.
Once you have a disk image, do a complete virus scan on the disk.

 

[RxyzM]

Normally a big corruption like you had is due a power failure or a dying disk. Check disk says your disk is good. So what caused the corruption?
You're trying to fix a windows installation, but you don't know what was the failing reason.
Do you have your data backed up?

You didn't gave us all the hardware specs (I asked on post #3)
I would put your disk on another desktop and do a disk image. If something goes wrong you can have have it back.
Once on the you have a disk image, do a complete virus scan on it.

Hi Megahertz07,

Sorry for that miss. I have just updated my profile with my system details. You may want to check that.

Will try the method that you have suggested this weekend. For me, normally weekend is reserved

Warm Regards,

Ravi

 

[RxyzM]

Back again from Cold

Hello Torchwood and Megahertz07,

I am back from cold. I retired from my current job a couple of months ago. Before that, could not spend much time with my machine due to job demands.

Have started working on this problem from last 2 weeks again. Following is progress so far -

- Needed to reinstall fonts. Once I completed that, The initial issue of missing windows startup screen, shrunk text etc. went away. I got the usual startup screen with four color blobs moving around with Starting Windows text.

- Restored ntuser.dat for my profile on the machine from my ntuser.dat.old. This solved my problem of not being able to login using my profile. In my profile, the wallpaper and the software icons appear as they used to appear before the crash.

Now I am struggling with following problems -

The repair install tells me that 4 programs (iTunes, NI - Electronic Workbench, Autocad and Acronis) would not work as expected and that I should uninstall them using programs and features option.

In programs and features, I cant find iTunes in the installed programs list; I can't uninstall Autocad as it points to disk for uninstaller that does not have autocad installed on it. NI - Electronic Workbench too does not appear in the Programs and Features screen and so is Acronis Trueimage.

The registry hives have entries for iTunes, NI - Electronic Workbench, Autocad and Acronis Trueimage.

I used CCleaner and Techutilities Registry checkers. Outputs from these 2 tools are poles apart. What CCleaner does not find, Techutilities tool finds those issues (Missing files, Missing COM/DCOM components etc.). CCleaner cleared some of the Missing files issues. Techutilities tool does not allow registration for some reason and hence can't use to fix the issues found by that tool.

I also tried to take out references to iTunes and Acronis Trueimage manually from registry (Really painful exercise :banghead. But, it seems that there are few entries that point to some device drivers. Windows could not be started normally after those changes. I reinstated the registry files from the backup taken before I started changing those entries in registry. The machine started working again (I am using the same machine for this note ).

The other 2 issues are -

SFC still fails with error (either online or in standalone DOS mode) with "Windows Resource protection could not perform..." issue.

Repair Install, as mentioned above, points to some programs for uninstallation and indicates some USB Ports may not work correctly after repair install completes.

But, in itself, the repair install fails in option "getting details of installed components". Error wording is to the effect of "could not get details for a component", but I do not see for which component it can not access details and from where? Is there any log that I can check for why it's failing?

Have been going through the articles after articles on this forum as well as some other forums, but I am not able to chart a path clearly as I am not sure whether it's registry corruption, file corruption, mixture of both, or mixture of both with ACL issue.

On the ACL front, I did run the Takeown command in standalone dos mode from Root of C: for all the subdirectories and files to add Administrators group to the owner's list. Also, ran icacls to reset the permissions as appropriate.

One thing that I noticed in all this is, somehow NT User\TrustedInstaller is missing from file permissions and in registry keys. Is this required entity in ACL list for Installers to work?

Thank you for your help and guidance so far. If you can guide me further, I will appreciate that.

With Warm Regards,

Ravi

 

[torchwood]

Hi Ravi,

lets try this a bit at a time,
silly question when your performing the repair install does your repair disk include SP1

Download
REVO uninstaller

remove the offending programs

not being able to find TrustedInstaller permissions could be part of the problem
from an elevated command mode, run this
net start trustedinstaller

whats the output.


Roy

 

[RxyzM]

Hi Roy,

I will try the steps you have suggested shortly and keep you posted.

Warm Regards,

Ravi

 

[RxyzM]

Hi Roy,

As I am doing a deeper dive in to system files, I think there is something weird that has happened in the file system. Need your valued advice to understand whether what I see is correct and usual directory structure in a good windows 7 OS.

As an example, please find below directory name too long error. Somehow, the "Application Data" directory repeats itself in the file name for about 5 times and then it ends with directory name.

The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\EmieBrowserModeList is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\History\History.IE5\MSHist012017110620171113 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Internet Explorer\DOMStore is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\History\History.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\Temporary Internet Files is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Temporary Internet Files\Content.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\History\History.IE5\MSHist012017110620171113 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\Temporary Internet Files\Content.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038 is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038\DeviceInfo is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0f4ed0be-76e0-4ab7-acd3-b30c1ef0f092\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\246fac5c-7f55-4383-9555-be275d0d43c7\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\b3004f87-774a-4cc6-9c51-89264da4ed5a\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceInformation\az-Latn-AZ is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceStage\Task\{A10D1647-AC70-478c-BA80-11DC14DC70BA} is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceInformation\az-Latn-AZ is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceStage\Task\{A10D1647-AC70-478c-BA80-11DC14DC70BA} is too long.
The directory name C:\Windows\System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\EmieBrowserModeList is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\History\History.IE5\MSHist012017110620171113 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Internet Explorer\DOMStore is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\History\History.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\Temporary Internet Files is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Temporary Internet Files\Content.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\History\History.IE5\MSHist012017110620171113 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\Temporary Internet Files\Content.IE5 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038 is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\00dd597a-807f-46d9-a4d9-76515e43a038\DeviceInfo is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0f4ed0be-76e0-4ab7-acd3-b30c1ef0f092\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\246fac5c-7f55-4383-9555-be275d0d43c7\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\b3004f87-774a-4cc6-9c51-89264da4ed5a\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceInformation is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceStage\Task\{A10D1647-AC70-478c-BA80-11DC14DC70BA} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\d0b60731-694a-408c-af09-7d08cd1445cc\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\0ecf2029-2c6a-41ae-9e0a-63ffc9ead877\DeviceStage\Task\{3aadc63a-477a-4adc-8b89-e002d0b48d1e} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Device Metadata\dmrccache\en-us\bc7efd47-636e-41ce-89a6-2a5ffb30ab5d\DeviceStage\Task\{A10D1647-AC70-478c-BA80-11DC14DC70BA} is too long.
The directory name C:\Windows\System32\config\systemprofile\Local Settings\Application Data\Application Data\Application Data\Application Data\Application

In the directory c:\windows\system32\config\systemprofile - The files "Application Data", "Cookies", "Nethood" etc. are JUNCTION links with files/directories in Appdata\Roaming directory. Please see the output of "DIR/p /A:s" command below as these files are marked with (S)ystem attribute.

Directory of C:\Windows\System32\config\systemprofile

07/14/2009 10:06 AM <DIR> AppData
01/21/2012 10:45 PM <JUNCTION> Application Data [C:\Windows\system32\con
fig\systemprofile\AppData\Roaming]
01/21/2012 10:45 PM <JUNCTION> Cookies [C:\Windows\system32\config\syste
mprofile\AppData\Roaming\Microsoft\Windows\Cookies]
01/21/2012 10:45 PM <JUNCTION> Local Settings [C:\Windows\system32\confi
g\systemprofile\AppData\Local]
01/21/2012 10:45 PM <JUNCTION> My Documents [C:\Windows\system32\config\
systemprofile\Documents]
01/21/2012 10:45 PM <JUNCTION> NetHood [C:\Windows\system32\config\syste
mprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts]
04/25/2018 11:31 PM 9,216 ntuser.dat.LOG1
07/14/2009 10:27 AM 0 ntuser.dat.LOG2
12/26/2010 01:26 PM 65,536 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TM.blf
12/26/2010 01:26 PM 524,288 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TMContainer00000000000000000001.regtrans-ms
12/26/2010 01:26 PM 524,288 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TMContainer00000000000000000002.regtrans-ms

01/21/2012 10:45 PM <JUNCTION> NetHood [C:\Windows\system32\config\syste
mprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts]
04/25/2018 11:31 PM 9,216 ntuser.dat.LOG1
07/14/2009 10:27 AM 0 ntuser.dat.LOG2
12/26/2010 01:26 PM 65,536 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TM.blf
12/26/2010 01:26 PM 524,288 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TMContainer00000000000000000001.regtrans-ms
12/26/2010 01:26 PM 524,288 ntuser.dat{a454f6fe-10c5-11e0-b366-806e6f
6e6963}.TMContainer00000000000000000002.regtrans-ms
Press any key to continue . . .
01/21/2012 10:45 PM <JUNCTION> PrintHood [C:\Windows\system32\config\sys
temprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts]
01/21/2012 10:45 PM <JUNCTION> Recent [C:\Windows\system32\config\system
profile\AppData\Roaming\Microsoft\Windows\Recent]
01/21/2012 10:45 PM <JUNCTION> SendTo [C:\Windows\system32\config\system
profile\AppData\Roaming\Microsoft\Windows\SendTo]
01/21/2012 10:45 PM <JUNCTION> Start Menu [C:\Windows\system32\config\sy
stemprofile\AppData\Roaming\Microsoft\Windows\Start Menu]
01/21/2012 10:45 PM <JUNCTION> Templates [C:\Windows\system32\config\sys
temprofile\AppData\Roaming\Microsoft\Windows\Templates]
5 File(s) 1,123,328 bytes
11 Dir(s) 20,263,464,960 bytes free

If i think about Microsoft\Windows\Template (and such) names, I tend to think that these directories are from "Program Files" and/or "ProgramData" directories. But I could be 100% wrong too.

Thank you for your help in advance. Really appreciate your inputs.

Warm Regards,

Ravi.

 

[RxyzM]

Hi Ravi,

lets try this a bit at a time,
silly question when your performing the repair install does your repair disk include SP1

Download
REVO uninstaller

remove the offending programs

not being able to find TrustedInstaller permissions could be part of the problem
from an elevated command mode, run this
net start trustedinstaller

whats the output.


Roy

Hi Roy,

I have tried the steps that you suggested and following is the outcome -
1. My Repair Disk does include SP1. If I use my original windows disk, I get an error in Repair Install "Current installation is more recent".

2. REVO Uninstaller - I downloaded and installed it. But, it doesn't find AUTOCAD.

3. For iTunes issue, I reinstalled iTunes (latest version) and uninstalled it. Now the Repair Install does not find iTunes as program that may not work after repair install.

I am trying all possible steps w/o touching the current setup as much as possible. :huh::shock:

Warm Regards,

Ravi