Doug,
I did some research on this before answering. Thanks to Eric Brodish [MSFT] for
this answer.
The answer, unfortunately, Doug is that there is very little control over where
Windows Update downloads the file before installation.
I can say that some parts of the situation can be manipulated as follows:
1. Windows Update will look for an NTFS drive before any others.
2. Windows Update will download to the drive with the largest amount of free
space.
Therefore, if you had two drives that had nearly identical amounts of free space
available, you could actually get into a situation in which one update downloads
on one drive, then the next update downloads on the other, and a third update
downloads back onto the first drive again.
Sincerely,
Pat Walters [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. Use
of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"doug" <> wrote in message
news:...
>I have a network drive which I share amoung my little LAN for "my" use.
>
> I have found that Windows Update has found this drive and uses it to store
> everything. I have room on my local drives for this, and do not apreciate
> my NetWork drive being hijacked like this.
>
> I couldn't find an INI easily, and I did a quick registry search and found
> tons of hits. It is assigning CAB files as being on the network drive.
> Where do I control where Windows Update writes the dpwnload files?
>
> doug
>
>
|