Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows 7 Home Premium: Repair Install fails with error

25 Nov 2017   #11
RxyzM

Windows 7 32 bit
 
 

Quote   Quote: Originally Posted by torchwood View Post
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


My System SpecsSystem Spec
.
25 Nov 2017   #12
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

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
My System SpecsSystem Spec
25 Nov 2017   #13
RxyzM

Windows 7 32 bit
 
 

Quote   Quote: Originally Posted by torchwood View Post
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

Warm Regards,

Ravi
My System SpecsSystem Spec
.

25 Nov 2017   #14
Megahertz07

Windows 7 HP 64
 
 

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.
My System SpecsSystem Spec
27 Nov 2017   #15
RxyzM

Windows 7 32 bit
 
 

Quote   Quote: Originally Posted by Megahertz07 View Post
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
My System SpecsSystem Spec
27 Apr 2018   #16
RxyzM

Windows 7 32 bit
 
 
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 ). 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
My System SpecsSystem Spec
28 Apr 2018   #17
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

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
My System SpecsSystem Spec
28 Apr 2018   #18
RxyzM

Windows 7 32 bit
 
 

Hi Roy,

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

Warm Regards,

Ravi
My System SpecsSystem Spec
08 May 2018   #19
RxyzM

Windows 7 32 bit
 
 

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.
My System SpecsSystem Spec
08 May 2018   #20
RxyzM

Windows 7 32 bit
 
 

Quote   Quote: Originally Posted by torchwood View Post
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.

Warm Regards,

Ravi
My System SpecsSystem Spec
Reply

 Windows 7 Home Premium: Repair Install fails with error




Thread Tools




Similar help and support threads
Thread Forum
Trying to repair install Windows 7 Home Premium 64 Bit.
Please read in its entirety before posting anything. As I will chronologically take you through my issue. Also I am very long winded but that is only because I am trying to be as clears as I possibly can be. For that, I apologize. Note, This is information anyone planning on posting might need...
Installation & Setup
Windows 7 Home Premium Fails to Update error 80073701
Since July 16 failed the Windows update. Every day Windows attempts to install updates every day it fails. Error code is 80073701. CBS.zip is too large, therefore, via this link: https://www.sendspace.com/file/wewb9x I have added a copy of the update history. It's in Dutch: Mislukt...
Windows Updates & Activation
Win7 home premium 64bit update fails, error 8007370B
Hi Folks, My Windows 7 home premium 64bit SP1 has failed to update since 2012. Every time I tried, the system update ended up with error code 8007370B: Windows Update encountered an unknown error. I have followed the steps at ...
Windows Updates & Activation
Windows 7 Home Premium Installation SP1 Fails Error Code:8024200D
Following the Windows Update Posting Instructions I have met a difficulty in that I see the maximum zip file upload is limited to 8MB. My CBS.zip file is 27.2MB and I would appreciate advice of any steps I should take before proceeding further. I have installed the System Update Readiness Tool...
Windows Updates & Activation
'Repair' install of Italian Home Premium 32-bit
I have a problem with an Italian Windows 7 32-bit Home Premium installation that I have been unable to resolve. So I am resorting to a 'repair' install. I downloaded the English Win 7 32-bit generic version as an ISO file and started to perform an 'upgrade' install. However, I didn't get...
Installation & Setup


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:35.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App