1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista Windows Update Issues

Discussion in 'Legacy Windows' started by jamo1133, 2011/03/27.

  1. 2011/03/27
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    I'm having problems with windows updates. I first posted to the "Malware & Virus Removal" thread - http://www.windowsbbs.com/showthread.php?t=98281. With Broni's help my computer is now clean but I am still having problems with Windows Update - his suggestion "In this forum, we make sure, your computer is free of malware and your computer is clean. Because the access to malware forum is very limited, your best option is to create new topic about your current issue, at Windows section. You'll get more attention." The following is what is happening:

    When I click on "windows update" from the Windows Security Center Box, it seems like a box is opening and closing very quickly. I don't see this if I click on "check for updates" from the control panel box.

    This is what I get when I click "turn automatic updating on or off "

    windows cannot find 'shell::::{26EE0668-A00A-44D7-9371-BEB064C98683}\10\::{36eef7db-88ad-4e81...\pageSettings'. Make sure you typed the name correctly, and then try again.
     
  2. 2011/03/28
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Please enter your System Details. It helps us in answering your questions!

    Start with running sfc /scannow from an elevated command prompt (Start > All Programs > Accessories, right-click Command Prompt and from the menu click Run as administrator).
     
    Arie,
    #2

  3. to hide this advert.

  4. 2011/03/28
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Thanks for responding. I've entered System Details, please let me know if you need to see more info. The CBS.log is huge so I am only posting current

    2011-03-28 18:16:49, Info CBS Scavenge: Package store indicates there is no component to scavenge, skipping.
    2011-03-28 19:14:17, Info CBS Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\cbscore.dll
    2011-03-28 19:14:17, Info CSI 00000001@2011/3/28:23:14:17.476 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef00f8c85 @0x7fef12f53ae @0x7fef12c3ed1 @0xff8749a8 @0xff8730c9 @0xff873578)
    2011-03-28 19:14:17, Info CSI 00000002@2011/3/28:23:14:17.492 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef00f8c85 @0x7fef13386cf @0x7fef13125d9 @0x7fef12c3feb @0xff8749a8 @0xff8730c9)
    2011-03-28 19:14:17, Info CSI 00000003@2011/3/28:23:14:17.492 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef00f8c85 @0x7fef13b838d @0x7fef13b84ba @0xff874207 @0xff873125 @0xff873578)
    2011-03-28 19:14:17, Info CBS NonStart: Checking to ensure startup processing was not required.
    2011-03-28 19:14:17, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xf8f990
    2011-03-28 19:14:17, Info CBS NonStart: Success, startup processing not required as expected.
    2011-03-28 19:14:17, Info CSI 00000005 CSI Store 878128 (0x00000000000d6630) initialized
    2011-03-28 19:14:22, Info CSI 00000006 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:22, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:23, Info CSI 00000008 Repair results created:
    POQ 0 starts:

    POQ 0 ends.
    2011-03-28 19:14:23, Info CSI 00000009 [SR] Verify complete
    2011-03-28 19:14:24, Info CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:24, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:24, Info CSI 0000000c [SR] Cannot verify component files for 0cf494171e89d3e4f35e13ef5a15a9eb, Version = 6.0.6001.22474, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:25, Info CSI 0000000d Repair results created:
    POQ 1 starts:

    POQ 1 ends.
    2011-03-28 19:14:25, Info CSI 0000000e [SR] Verify complete
    2011-03-28 19:14:26, Info CSI 0000000f [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:26, Info CSI 00000010 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:27, Info CSI 00000011 Repair results created:
    POQ 2 starts:

    POQ 2 ends.
    2011-03-28 19:14:27, Info CSI 00000012 [SR] Verify complete
    2011-03-28 19:14:28, Info CSI 00000013 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:28, Info CSI 00000014 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:29, Info CSI 00000015 [SR] Cannot verify component files for 2175dcfc2a0a000218a3ee7d802e9551, Version = 6.0.6001.22474, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:29, Info CSI 00000016 Repair results created:
    POQ 3 starts:

    POQ 3 ends.
    2011-03-28 19:14:29, Info CSI 00000017 [SR] Verify complete
    2011-03-28 19:14:30, Info CSI 00000018 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:30, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:32, Info CSI 0000001a Repair results created:
    POQ 4 starts:

    POQ 4 ends.
    2011-03-28 19:14:32, Info CSI 0000001b [SR] Verify complete
    2011-03-28 19:14:32, Info CSI 0000001c [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:32, Info CSI 0000001d [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:32, Info CSI 0000001e [SR] Cannot verify component files for 2e7a2b0f7852956b6e5b4910f142be3b, Version = 6.0.6001.18331, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:33, Info CSI 0000001f [SR] Cannot verify component files for 2fa8eb5ebac1b2d7c4059dff16444cd7, Version = 6.0.6001.18292, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:33, Info CSI 00000020 Repair results created:
    POQ 5 starts:

    POQ 5 ends.
    2011-03-28 19:14:33, Info CSI 00000021 [SR] Verify complete
    2011-03-28 19:14:34, Info CSI 00000022 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:34, Info CSI 00000023 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:35, Info CSI 00000024 [SR] Cannot verify component files for 3c7c20993f206233a8e305785074c8a3, Version = 1.1.6000.16782, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:6595b64144ccf1df}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:35, Info CSI 00000025 [SR] Cannot verify component files for 3e831e1a5a2de4e2d132cde2c0092fff, Version = 1.0.6001.18175, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:6595b64144ccf1df}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:35, Info CSI 00000026 Repair results created:
    POQ 6 starts:

    POQ 6 ends.
    2011-03-28 19:14:35, Info CSI 00000027 [SR] Verify complete
    2011-03-28 19:14:36, Info CSI 00000028 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:36, Info CSI 00000029 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:37, Info CSI 0000002a Repair results created:
    POQ 7 starts:

    POQ 7 ends.
    2011-03-28 19:14:37, Info CSI 0000002b [SR] Verify complete
    2011-03-28 19:14:37, Info CSI 0000002c [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:37, Info CSI 0000002d [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:39, Info CSI 0000002e Repair results created:
    POQ 8 starts:

    POQ 8 ends.
    2011-03-28 19:14:39, Info CSI 0000002f [SR] Verify complete
    2011-03-28 19:14:39, Info CSI 00000030 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:39, Info CSI 00000031 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:39, Info CSI 00000032 [SR] Cannot verify component files for 5043c633c470748a7b48deb379137ae5, Version = 1.0.6000.16782, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:6595b64144ccf1df}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:41, Info CSI 00000033 Repair results created:
    POQ 9 starts:

    POQ 9 ends.
    2011-03-28 19:14:41, Info CSI 00000034 [SR] Verify complete
    2011-03-28 19:14:41, Info CSI 00000035 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:41, Info CSI 00000036 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:42, Info CSI 00000037 Repair results created:
    POQ 10 starts:

    POQ 10 ends.
    2011-03-28 19:14:42, Info CSI 00000038 [SR] Verify complete
    2011-03-28 19:14:43, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:43, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:44, Info CSI 0000003b Repair results created:
    POQ 11 starts:

    POQ 11 ends.
    2011-03-28 19:14:44, Info CSI 0000003c [SR] Verify complete
    2011-03-28 19:14:45, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:45, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:45, Info CSI 0000003f [SR] Cannot verify component files for 6c164a56097bbdb47aa7a52303190bab, Version = 6.0.6000.16922, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:46, Info CSI 00000040 Repair results created:
    POQ 12 starts:

    POQ 12 ends.
    2011-03-28 19:14:46, Info CSI 00000041 [SR] Verify complete
    2011-03-28 19:14:47, Info CSI 00000042 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:47, Info CSI 00000043 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:47, Info CSI 00000044 [SR] Cannot verify component files for 745307ce115d90a4eff6a6d4a005eed5, Version = 6.0.6001.18292, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:48, Info CSI 00000045 Repair results created:
    POQ 13 starts:

    POQ 13 ends.
    2011-03-28 19:14:48, Info CSI 00000046 [SR] Verify complete
    2011-03-28 19:14:49, Info CSI 00000047 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:49, Info CSI 00000048 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:50, Info CSI 00000049 Repair results created:
    POQ 14 starts:

    POQ 14 ends.
    2011-03-28 19:14:50, Info CSI 0000004a [SR] Verify complete
    2011-03-28 19:14:50, Info CSI 0000004b [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:50, Info CSI 0000004c [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:52, Info CSI 0000004d Repair results created:
    POQ 15 starts:

    POQ 15 ends.
    2011-03-28 19:14:52, Info CSI 0000004e [SR] Verify complete
    2011-03-28 19:14:52, Info CSI 0000004f [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:52, Info CSI 00000050 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:53, Info CSI 00000051 [SR] Cannot verify component files for 9a5b2f7259b328d681e18ee5b10336be, Version = 6.0.6001.18292, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:53, Info CSI 00000052 Repair results created:
    POQ 16 starts:

    POQ 16 ends.
    2011-03-28 19:14:53, Info CSI 00000053 [SR] Verify complete
    2011-03-28 19:14:54, Info CSI 00000054 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:54, Info CSI 00000055 [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:55, Info CSI 00000056 [SR] Cannot verify component files for a1940ca48cfc6b40d389aab8b053300f, Version = 6.0.6002.18111, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:55, Info CSI 00000057 Repair results created:
    POQ 17 starts:

    POQ 17 ends.
    2011-03-28 19:14:55, Info CSI 00000058 [SR] Verify complete
    2011-03-28 19:14:55, Info CSI 00000059 [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:55, Info CSI 0000005a [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:56, Info CSI 0000005b [SR] Cannot verify component files for a8b94e261bcb74589ba8c38457b1c55c, Version = 6.0.6000.16927, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
    2011-03-28 19:14:57, Info CSI 0000005c Repair results created:
    POQ 18 starts:

    POQ 18 ends.
    2011-03-28 19:14:57, Info CSI 0000005d [SR] Verify complete
    2011-03-28 19:14:57, Info CSI 0000005e [SR] Verifying 100 (0x0000000000000064) components
    2011-03-28 19:14:57, Info CSI 0000005f [SR] Beginning Verify and Repair transaction
    2011-03-28 19:14:59, Error CSI 00000060 (F) STATUS_OBJECT_NAME_NOT_FOUND #1406828# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (STANDARD_RIGHTS_READ|FILE_READ_ATTRIBUTES), oa = @0x16bce50->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[97] "\??\C:\Windows\WinSxS\amd64_aspnet_compiler_b03f5f7f11d50a3a_6.0.6002.18005_none_d0f56c0f446641b5 "; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x16bce30, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = 0x00004000, eab = NULL, eal = 0, disp = Invalid)
    [gle=0xd0000034]
    2011-03-28 19:14:59, Error CSI 00000061@2011/3/28:23:14:59.066 (F) d:\longhorn\base\wcp\sil\merged\ntu\ntsystem.cpp(1849): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    [gle=0x80004005]
    2011-03-28 19:15:04, Error CSI 00000062 (F) STATUS_OBJECT_NAME_NOT_FOUND #1406827# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
    2011-03-28 19:15:04, Error CSI 00000063 (F) STATUS_OBJECT_NAME_NOT_FOUND #1406826# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x16bd748->SIL_OBJECT_ATTRIBUTES {s:40; on: "amd64_aspnet_compiler_b03f5f7f11d50a3a_6.0.6002.18005_none_d0f56c0f446641b5 "; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
    [gle=0xd0000034]
     
  5. 2011/03/29
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    You skipped the
    part

    I never asked for a CBS.log.

    Did you run the SFC command?
     
    Arie,
    #4
  6. 2011/03/29
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Yes I did run the SFC, you're right you didn't ask for the CBS log, sorry about that

    I'm not exactly sure what step you are talking about, I don't see that in your original reply
     
  7. 2011/03/29
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Hi jamo,

    From the link Arie provided (system details)...

     
  8. 2011/03/29
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Thank you!
     
  9. 2011/04/04
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Ran the sfc scan, it stopped after 14% complete then issued the message "Windows Resource Protection found corrupt files but was unable to fix them.
     
  10. 2011/04/04
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Do you have a Factory recovery disk or an original Vista disk?

    Also it gets a little confusing if you supply seemingly contradicting posts

    Why didn't you report...

    ... the above (last week) when you ran SFC or is this something new, and if so what's happened in the last 6 days that caused you to run SFC again?

    @Evan, do you want to step in here... You've suffered from this issue in the past.
     
    Last edited: 2011/04/04
  11. 2011/04/04
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Sorry for the contradicting posts. I wasn't asked to post anything from the original request so I thought results would be helpful so I ran the scan again, same result when I ran the first time.

    I have a Dell factory CD
     
  12. 2011/04/04
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    Fair enough, does this CD give the option of a repair install (non destructive)?
     
  13. 2011/04/04
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    No, it gives me the option of doing a factory image restore or a reinstall of windows vista
     
  14. 2011/04/04
    wildfire

    wildfire Getting Old

    Joined:
    2008/04/21
    Messages:
    4,649
    Likes Received:
    124
    I've PM'd someone who had a similar issue a few years ago. Be patient hopefully he'll chime in.
     
  15. 2011/04/04
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,919
    Likes Received:
    511
    Hi jamo1133. Yikes this doesn't look to good. Since sfc couldn't fix the corrupt files you could try running chkdsk /r from command prompt and seeing if that helps fix your particular issue.

    Click Start< All Programs< Accessories< Right click Command Prompt and click Run as Administrator. Once the command prompt window opens type chkdsk /r and pres enter. If you are prompted to reboot the machine go ahead and do so. Check Disk will run during the next reboot.

    After the machine reboots see if you experience the same issue.

    If running Check Disk makes no difference then try running the Microsoft Fix It Tool from this link, How do I reset Windows Update components?
     
    Last edited: 2011/04/04
  16. 2011/04/10
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Hi Evan, chkdsk did not resolve the issue. I tried running the Microsoft Fit It Tool but got msg "service 'windows update' (WUAUSERV) failed to start. Verify you have sufficient privileges to start system services. "
     
  17. 2011/04/10
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,919
    Likes Received:
    511
    Did you run the Fix It Tool in normal mode? Try Saving the tool to your desktop and right click it and select Run As Administrator. See if it runs now.
     
  18. 2011/04/10
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    Yes, I ran in normal mode. I just tried saving it to the desktop but when I right click I don't see an option to Run As Administrator.
     
  19. 2011/04/10
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,919
    Likes Received:
    511
    Right click the program and click properties. Now click on the Compatibility tab. Place a check mark in the checkbox that says Run As Administrator. Click ok to close the properties window. Now run the program.

    Also do you have UAC enabled?
     
  20. 2011/04/10
    jamo1133

    jamo1133 Inactive Thread Starter

    Joined:
    2011/03/20
    Messages:
    81
    Likes Received:
    0
    I guess its the install that I am getting the error on. The file I saved to my desktop is "microsoftfixit50202.msi ". When I right click on it I see "install, repair, uninstall, open with, etc., properties. When I click on properties, I see the following tabs, general, digital signatures, security, custom, details'.

    Yes, UAC is enabled. I tried turning it off and installing the tool but got the same error.
     
  21. 2011/04/10
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,919
    Likes Received:
    511
    Try enabling the built in Administrator Account. Once the account has been enabled go ahead and log into the account and see if running the Fix It Tool will work from that account this time.

    If the tool still doesn't run go ahead and visit the How do I reset Windows Update components link in my first post. Instead of running the Fix It Tool perform the manual steps in the article to reset the Windows Update Components.
     
    Last edited: 2011/04/10

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.