Results 1 to 6 of 6

Thread: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

  1. #1
    WindowsUpdate_0000052F Guest

    "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    Yes a here in the registry is the reference of a drive installed.
    Problem found!
    Windows Registry Editor Version 5.00

    1) regedit (Always backup the Registry before you edit it!)
    2) find key below or something similar
    ---------------------
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Delivery\{90850409-6000-11D3-8CFE-0150048383C9}]
    ----------------------
    3) Below is the wrong reference "F" I remove drive "F"
    Changed it to a valid Drive letter .. in my case it was "E"

    ---------------------- = was
    "LocalCacheDrive"="F"
    ---------------------- = was

    ---------------------- = now
    "LocalCacheDrive"="E"
    ---------------------- = now

    This fixed the issue & the update was able to run.

  2. #2
    PA Bear [MS MVP] Guest

    Re: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    What issue? Which update?

  3. #3
    bbrecken Guest

    RE: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    If I only have one drive, presumably this should be C instead of E but this
    is not at all clear from the description. Also, as PA Bear points out, it is
    not even clear what the issue is. How did the LocalCacheDrive get created
    incorrectly? Is this from when HP installed my operating system and
    incorectly specified E as a LocalCacheDrive? I know I never specified this.

  4. #4
    bbrecken Guest

    RE: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    I specified "LocalCacheDrive" = "C" because that's the only drive I have. At
    first, I received a whole bunch of Windows Internet Explorer windows that
    were telling me I needed an ActiveX control but there was no way to install
    or run it. I closed all of those windows by clicking the closebox with my
    mouse since I couldn't close them any quicker than they opened with the
    Alt-F4 key sequence on the keyboard. It was kind of scarey. It reminded me
    of a trojan horse virus a few years back (about 2004), where IE windows kept
    opening until all of the available resources were utilized and the machine
    locked up. Anyway, once I was able to close all of these IE warning windows,
    I additionally added prompts for ActiveX Controls, so next time there will
    hopefully be a way to run the ActiveX control, instead of IE just continuing
    to warn me without recourse. I did this by following these intructions from
    Microsoft (you can probably find them, or something close to them, too):
    Click to open Internet Explorer.
    1. Click the Tools button, and then click Internet Options.
    2. Click the Security tab, and then click Custom level.
    3. Do one or both of the following:
    o To turn off the Information bar for ActiveX controls, scroll to the
    ActiveX controls and plug-ins section of the list, and then, under Automatic
    prompting for ActiveX controls, click Enable.
    o To turn off the Information bar for file downloads, scroll to the
    Downloads section of the list, and then, under Automatic prompting for file
    downloads, click Enable.
    4. Click OK, click Yes to confirm that you want to make the change, and then
    click OK again.
    Now, the Office updates completed and I don't have IE windows popping up
    uncontrollably. Not sure whether the two incidents are related but they
    seemed related in my case.

  5. #5
    Greg Guest

    RE: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    Very helpful to me.

    In the registry I found the "LocalCacheDrive" in other place with search.
    And change the drive id to be my current any local drive. (in my case, my
    original localcachedrive is gone)
    After change, my problem was fixed.

  6. #6
    Join Date
    Nov 2009
    Posts
    1

    Re: "WindowsUpdate_0000052F" "WindowsUpdate_dt000" The FIX!

    I have an update to this. On my windows 7 machine I found this entry at :

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\11.0\Delivery\{90110409-6000-11D3-8CFE-0150048383C9}

    Just like the original poster stated the drive letter was incorrect and changing the drive letter fixed the issue.

    If you are unable to find the entry just search for "LocalCacheDrive" w/out quotes.

Similar Threads

  1. Replies: 5
    Last Post: 05-04-2011, 08:26 AM
  2. Replies: 6
    Last Post: 18-05-2010, 12:27 AM
  3. Replies: 4
    Last Post: 12-05-2009, 03:26 PM
  4. Replies: 1
    Last Post: 01-05-2009, 02:57 AM
  5. Replies: 1
    Last Post: 06-11-2007, 02:18 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,272,719.17463 seconds with 17 queries