Prev: Update KB933666
Next: WindowsUpdate_8024402C WindowsUpdate_dt000
From: Tergiver on 14 Jun 2007 09:01
Installing the updates separately worked for me as well.

How did you move 'users' to a separate partition? I have a system partition,
program files partition, and a 'data' partition which I used the Location tab
of the folder properties on things like Contacts, Desktop, Documents, Music,
Pictures, etc. to move each of them individually, but there is no Location
tab for each user, or for the Users folder.

"Erik Mikkelson" wrote:

>
>
> "Jordan Moss" wrote:
>
> > Could someone please explain what 80070011 means all my updates are failing
> > with this error after reboot.
>
> I had the same problem, until I decided to try installing each update in
> isolation. For some reason that worked. It takes a while to get through all
> of them (especially if you need to reboot), but it *will* work eventually.
>
> I have a configuration where I have partitioned the heck out of my drive in
> order to better control where things are on it. I have a primary swap
> partition, then a primary windows partition, then an extended partition with
> 3 logical drives, one for program files, one for users, and one for temporary
> files/downloads. The 3 extended partitions are set up as ntfs paths on the
> windows partition, so it looks to any program that I'm just running with one
> big drive (but defragmenting takes a quarter of the time).
>
> This strange drive configuration probably caused my issue, and perhaps
> something similar caused yours.
>
> I only know that installing each update in isolation worked just fine.
From: sms4001 on 19 Jun 2007 03:15

from what I have read from everyone else having this problem its because
we all moved our program files to a different drive and or partition as
the one that has windows on it. seems pretty dumb that windows update
cant adapt to that but i guess thats how it is. is there any way to
contact Microsoft about this and possibly get them to fix it?


--
sms4001
------------------------------------------------------------------------
sms4001's Profile: http://forums.techarena.in/member.php?userid=26907
View this thread: http://forums.techarena.in/showthread.php?t=697961

http://forums.techarena.in

From: jyinAtlantaIN on 20 Jun 2007 02:04
Yes, please Microsoft, fix windows update to understand how to deal with
having program files and users on a different partition. You have to know
that it makes a lot of sense to partition the system that way.

All of my updates are failing too. I have my program files and users on a
separate partition from the OS.

Jim

"sms4001" wrote:

>
> from what I have read from everyone else having this problem its because
> we all moved our program files to a different drive and or partition as
> the one that has windows on it. seems pretty dumb that windows update
> cant adapt to that but i guess thats how it is. is there any way to
> contact Microsoft about this and possibly get them to fix it?
>
>
> --
> sms4001
> ------------------------------------------------------------------------
> sms4001's Profile: http://forums.techarena.in/member.php?userid=26907
> View this thread: http://forums.techarena.in/showthread.php?t=697961
>
> http://forums.techarena.in
>
>
From: alantangcs on 21 Jun 2007 06:04
Hello all,

I've been having to live with this nuisance for months now, until the
nuisance became a problem today when my network access was blocked
because I do not have the latest security patches. I too have
installed Program Files in another partition.

However, after some playing around with this today, I may be coming
close to a workaround. Perhaps some of you could take a look at this
and we can work together to solve this problem.

Windows Update occasionally has to update programs and services which
are already running. This can't happen so what it does is it stores
the update instructions in a file called "C:\Windows\WinSXS
\Pending.XML" and prompts for a reboot. On reboot, a program called
"C:\Windows\System32\POQExec.exe" fires up and executes these
instructions.

The "WinSXS" folder is protected so that not even an admin can modify
the files. However, if you are an admin of the machine, you can take
ownership of the "Pending.XML" file and give yourself full control of
the file. If you don't see a "Pending.XML" file, it's probably
because the file got cleaned up when Windows Update started and
notified you that the update failed. You need to force that file to
be created again. Start Windows Update, and select one of the patches
that keep failing and install it. When it asks you to reboot... do
NOT reboot yet. Take ownership of the file and give yourself full
control.

Before today, I've been looking through "C:\Windows\WindowsUpdate.log"
and got stumped at this error message:

"WARNING: Got extended error: "POQ Operation
hardLinkFile OperationData \SystemRoot\WinSxS\...... \??\D:
\Program Files...."

(I cut out the full file paths because I'm not working on the
problematic Vista machine so I can't copy/paste).

What is the "\??\" prefix was doing in front of "D:\Program Files"?
Was Windows Update trying to copy files to "\??\D:\Program Files"? Is
that causing the failure?

So I opened up Pending.XML and sure enough, there were all these
references to "\??\D:\Program Files". I did a find/replace so the
paths didn't have the "\??\" in front of it. Saved the file, and
rebooted the machine.

Well, to my dismay, that did not solve the problem. If you look
through WindowsUpdate.Log now, you will notice that it is now trying
to operate on "D:\Program Files" rather than "\??\D:\Program Files".

Perhaps more people experimenting on this will increase our chances of
finding a temporary work around until Microsoft fixes this? If anyone
could shed any light on "POQExec", the "HardLinkFile" operation or
have any other ideas, that would help heaps.

From: alantangcs on 22 Jun 2007 02:14
Everyone! I have successfully installed KB931099 with ProgramFiles on
D:.

Please follow these instructions at your own risk. If you aren't
feeling confident, I recommend you back up your system.

Pre-requisites: You need to be an administrator on the machine.

Here's what you do:

- Start Windows Update.
- Click "Check for updates" in the top left corner.
- Click the "View Available Updates" link.
- Select KB931099 ONLY. Deselect any other patches that have been
failing in the past.
- Click Install.

Windows Update now downloads the patch.

- Do ***NOT*** restart the computer. Close Windows Update.

Windows Update also created C:\Windows\WinSXS\Pending.XML which you
now need to modify. To make your life difficult, the SYSTEM account
owns the whole WinSXS folder so not even admin's can modify the files
inside... unless you take ownership of the folder. To do that:

- Open up an explorer window and browse to C:\Windows\WinSXS
- Right-click on "Pending.XML" and select properties.
- In the dialog, click on the "Security" tab
- Click "Advanced" down the bottom
- In the new dialog, select the "Owner" tab. Notice the owner is
SYSTEM.
- Click "Edit".
- In the "Change Owner To" list, select the user account you are
currently using (you must be an admin)
- Click OK. Some warnings might pop up. Just ignore them. Close the
"Advanced Security Settings" dialog.
- Back on the "Pending.XML Properties" dialog, you should now be able
to give yourself full control of the file.
- Click the "Edit" button.
- In the new dialog, click "Add" and enter your user name. Click OK.
- Your user name should now appear in the list. Select it and check
the "Full Control" button.
- Click Ok, and Ok (closing any warning popups).

Now you fully control Pending.XML.

- Open "Pending.XML" in notepad.

Now onto some explanation:

Windows Update downloads the patches into C:\Windows\WinSXS. You will
notice in Pending.XML several "HardLinkFile" tags in the XML file.
The source is "\SystemRoot\WinSxS\..." followed by a long folder name
containing the patch files. Your system root should be "C:\Windows"
but it could be different if you chose to install Windows on another
drive other than C.

If your program files is on a drive other than the system drive, the
HardLinkFile operation fails. The HardLinkFile operation acts like a
fake-copy. It links the destination with the source file without
actually copying the file content. The source and destination must be
on the same partition.

Looking at Pending.XML again:

<HardLinkFile source="\SystemRoot\WinSxS\........."
destination="\??\D:\Program Files\........." ... />

this is bound to fail.

However, fixing this problem is not hard. The HardLink operation will
succeed if the patch files are on the same drive as Program Files.

- Note the long cryptic folder name from the source from after the
WinSxS. On my computer, this is "x86_security-malware-windows-
defender_31bf3856ad364e35_6.0.6000.16420_none_55c0ce805b18c568" but it
might be different on yours.
- You need to locate this physical folder in the WinSxS folder. Once
you find it, copy it to "D:\Temp" (NOTE!!! If your program files is
on another drive, say X:, then this will be X:\Temp for you).

Easy enough? Still have Pending.XML open in notepad? Now you need to
redirect the instructions to use the files on D: rather than C:... but
WAIT! Look at the file closely and you'll notice some other
instructions.

On my computer, I also moved "ProgramData" to D: so one thing I
noticed is there is a HardLinkFile instruction that uses "\??\C:". I
had to replace this with "\??\D:". You will also notice 2 MoveFile
commands for this patch. They both move files from a folder under
SystemRoot to another folder under SystemRoot. This instruction
should work without any modifications so we shouldn't touch them.

- The safest way to do this is to do a Replace (in notepad). Replace

HardLinkFile source="\SystemRoot\WinSxS"

.... with...

HardLinkFile source="\??\D:\Temp"

This ensures the MoveFile lines are not affected.

If you are trying to adapt these instructions for other patches, make
sure you check the file for other oddities.

- Save and close Pending.XML.
- Reboot the machine.

After the machine is booted up, check C:\Windows\WinSxS\POQExec.log
for any errors. If an error occurred, you should also notice the tool
tip window saying "Windows Update Failed" (or something like that).
If that's the case, you either did something wrong, or I left
something out. Either way, you don't have to worry too much as
Windows Update uses a transaction system. If any instruction fails
(even if after an instruction succeeded), none of the changes in the
entire patch take place (so you are free to try again).

Just to make sure, start Windows Update and click "Check for
Updates". If KB931099 no longer appears... congratulations, you have
just worked around one of the most annoying limitations of Windows
Update.

 | 
Pages: 1
Prev: Update KB933666
Next: WindowsUpdate_8024402C WindowsUpdate_dt000