I applied my patches using a .cmd file with the following commands and did not have any issues. rem rem October 2005 Update rem WindowsServer2003-KB905495-x86-ENU.exe /quiet /norestart WindowsServer2003-KB905414-x86-ENU.exe /quiet /norestart WindowsServer2003-KB899589-x86-ENU.exe /quiet /norestart WindowsServer2003-KB901017-x86-ENU.exe /quiet /norestart WindowsServer2003-KB900725-x86-ENU.exe /quiet /norestart WindowsServer2003-KB904706-x86-ENU.exe /quiet /norestart WindowsServer2003-KB902400-x86-ENU.exe /quiet /norestart WindowsServer2003-KB896688-x86-ENU.exe /quiet /norestart Dirk Blose, MCSE, CCA Lead Technical Analyst (919) 765-4791 dirk.blose@xxxxxxxxxx >>> CMSchneider@xxxxxxxxx 10/25/05 9:06 AM >>> st1\:*{behavior:url(#default#ieooui) }The current critical Microsoft patches. Since the last set, it installed, I allowed it to, not knowing, the new updater/installer. Since then, and time a patch is applied, that requires a reboot, it continues to prompt for a reboot, every X minutes, until you do. The users also get this prompt, when making connections to published applications on the servers, but the button is grayed out and they are hung and can not close it. From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Dirk Blose Sent: Tuesday, October 25, 2005 7:48 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: M$ Patches Which patches are you referring to? I was able to control the reboots with this last round of Patches on 2003 servers. Dirk Blose, MCSE, CCA Lead Technical Analyst (919) 765-4791 dirk.blose@xxxxxxxxxx >>> CMSchneider@xxxxxxxxx 10/25/05 8:43 AM >>> With the changes to the updater*I now am forced to have to reboot my servers as soon as I patch a server, whereas before, I could patch, wait for the weekly reboot and be done. Now I must coordinate downtime of 70+ servers in a 24x7x365 environment. This makes me less than pleased. Anyone have a way around this? Chad