M
Mike Coppins
Hi, I'm using Windows Vista Business 32-bit. I have 6 updates that
always fail to install, each one complaining of error 80070011.
A bit of googling gives me this info:
I have a multiple partition setup:
C drive, Vista system, 20GB NTFS
D drive, Win2k system, 4GB NTFS
E drive, Apps + Data partition, rest of disk (300 or so GB)
All partitions have lots of space.
I do have Program Files / Common Files junctioned off to E drive, and
HKLM > SOFTWARE > MS > WINDOWS > CURRENTVERSION entries for those
folders pointing in the correct places on E drive, but I have tried
taking all this apart and having the right files on C drive and registry
entries back to their defaults but the error persists.
The Windows Defender updates always install successfully though,
regardless of Program Files / Common Files pointing to E:.
I have used this type of setup on Windows 2000 and XP for years without
problems like this. Any ideas what I can do to resolve it, short of
blowing away the whole installation and starting again?
always fail to install, each one complaining of error 80070011.
A bit of googling gives me this info:
# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x11
# for hex 0x11 / decimal 17
ERROR_NOT_SAME_DEVICE winerror.h
# The system cannot move the file to a different disk drive.
# 1 matches found for "0x80070011"
I have a multiple partition setup:
C drive, Vista system, 20GB NTFS
D drive, Win2k system, 4GB NTFS
E drive, Apps + Data partition, rest of disk (300 or so GB)
All partitions have lots of space.
I do have Program Files / Common Files junctioned off to E drive, and
HKLM > SOFTWARE > MS > WINDOWS > CURRENTVERSION entries for those
folders pointing in the correct places on E drive, but I have tried
taking all this apart and having the right files on C drive and registry
entries back to their defaults but the error persists.
The Windows Defender updates always install successfully though,
regardless of Program Files / Common Files pointing to E:.
I have used this type of setup on Windows 2000 and XP for years without
problems like this. Any ideas what I can do to resolve it, short of
blowing away the whole installation and starting again?