.NET 3.5.1 security updates don't appe...
older-than-dirt
19 Feb 2013
Hello All,
I've had the occasion to bring up 2 systems (Win 7), (1) x86 and (1) x64 from Win 7 to SP1 and then run Autopatcher (Jan 2013) with the Feb updates dated from last Sunday's release scripts.
The following 2 patches don't install and when being run by Autopatcher, they put up a help message displaying the command line parameter usage. I believe this is due to using incorrect parameters. This happened on both the x86 and the x64 systems. Dismissing the dialog allowed AP to continue installing to completion, but the patches were not installed.
The 2 patches are:
KB2756921
KB2789645
Both are .NET 3.5.1 security patches.
As a side note, when I first ran AP, I checked off all Critical and Recommended updates (~ 105 total, IIRC) and Windows choked and died with this large amount. I allowed it to revert and then reran AP only applying Critical and then a second round applying Recommended. The OS handled this better. This is not a fault with AP, just a heads up for anyone else attempting this.
Also, I found a bug when selecting a particular patch and then clicking on the "Note" hyperlink at the bottom, AP crashed. I am sorry I don't have a log file. These machines are not connected to the internet, but they do have a live network connection.
Hopefully this info helps.
Thanks again for all of the hard work..
I've had the occasion to bring up 2 systems (Win 7), (1) x86 and (1) x64 from Win 7 to SP1 and then run Autopatcher (Jan 2013) with the Feb updates dated from last Sunday's release scripts.
The following 2 patches don't install and when being run by Autopatcher, they put up a help message displaying the command line parameter usage. I believe this is due to using incorrect parameters. This happened on both the x86 and the x64 systems. Dismissing the dialog allowed AP to continue installing to completion, but the patches were not installed.
The 2 patches are:
KB2756921
KB2789645
Both are .NET 3.5.1 security patches.
As a side note, when I first ran AP, I checked off all Critical and Recommended updates (~ 105 total, IIRC) and Windows choked and died with this large amount. I allowed it to revert and then reran AP only applying Critical and then a second round applying Recommended. The OS handled this better. This is not a fault with AP, just a heads up for anyone else attempting this.
Also, I found a bug when selecting a particular patch and then clicking on the "Note" hyperlink at the bottom, AP crashed. I am sorry I don't have a log file. These machines are not connected to the internet, but they do have a live network connection.
Hopefully this info helps.
Thanks again for all of the hard work..
click-click
19 Feb 2013
Looks like .msu files no longer accepts /q as a valid switch. For now, just run manually by executing the .msu files
Windows6.1-KB2756921-x86.msu
Windows6.1-KB2789645-x86.msu.
from \dotNET-x86_files. The same goes for x64 and they should install.
Windows6.1-KB2756921-x86.msu
Windows6.1-KB2789645-x86.msu.
from \dotNET-x86_files. The same goes for x64 and they should install.
ViroMan
21 Feb 2013
it may not recognize /q but what about /quiet? The link here -> http://support.microsoft.com/kb/934307
click-click
21 Feb 2013
Of course. Already fixed this on Tuesday for all .msu files via a silent update.
Edited by click-click, 21 February 2013 - 01:54 PM.
Edited by click-click, 21 February 2013 - 01:54 PM.
