Hi Susan--just got home--I'll check a couple of things and post back. There could be a difference in software, but not very likely--the one big thing that I mentioned was that one server that didn't BSOD also didn't get the KB2975719 installed at the same time with the rest of the updates because our network admin didn't select it for installation, and because that one points straight to MS for updates, it wasn't automatically selected/checked (due to approval on WSUS for the others). Before attempting to separate the updates, I did test going the route of clearing updates cache and pointing straight to MS on another server to install all at once, but that didn't fix anything (that one BSOD'd also).
BTW, I should mention that except for a few servers where some updates have failed on the first round (but installed on try 2), all of our WS08R2, WS08, and WS03R2 servers have not had update issues this month (knocking on wood as I type this)--another reason I was looking at the rollup for 12&12R2. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: Thursday, August 14, 2014 2:03 PM To: [email protected] Subject: Re: [NTSysADM] August Update issues If you wouldn't mind some sleuthing... open up fntcache.dat on each machine/compare the one that didn't bsod to the ones that did. Is there a difference? Susan Bradley Still migrating the msmvps.com blogs but we're getting closer. blogs.msmvps.com/bradley is the new url and redirects are in place Have I mentioned how much migrations are REALLY painful? On 8/14/2014 1:57 PM, Susan Bradley wrote: > What software do you have installed on everything - but- one - server? > > I'm trying to figure out a commonality and just can't figure out a > trigger. > > Susan Bradley > Still migrating the msmvps.com blogs but we're getting closer. > blogs.msmvps.com/bradley is the new url and redirects are in place > Have I mentioned how much migrations are REALLY painful? > > On 8/14/2014 1:47 PM, Miller Bonnie L. wrote: >> Thanks for the update Susan (and thanks for helping everyone on the >> forums too--you seem to be fielding everything!). That is good to >> know if we run into the win7 issue at all, but we'll probably hold >> back now until MS can sort the issue a bit better--I'm sure it won't >> take too long. >> >> I haven't had any servers that didn't recover, and it's slightly >> different than what I see being posted about win7 workstations, but >> still points to win32k.sys. I've not had issues by installing >> updates in separate sets/rounds, so thought that might help others >> and was posting here as it's server related (I'm on wsus, but not >> patch mgmt.--may have to add that one). >> >> In particular, the issue with the 2012 non-R2 servers not really >> updating is key--we at least needed to get the security updates to >> load, and I might not have noticed it right away if not digging into >> the other issue. >> >> -B >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Susan Bradley >> Sent: Thursday, August 14, 2014 1:36 PM >> To: [email protected] >> Subject: Re: [NTSysADM] August Update issues >> >> Patchmanagement.org is the update news list :-) >> >> >> I could solve it by booting from a DVD and removing the following file: >> >> c:\Windows\System32\FNTCACHE.DAT >> >> >> So that reportedly is working for some. >> >> >> >> >> On 8/14/2014 1:30 PM, Miller Bonnie L. wrote: >>> Surprisingly, I hadn't seen anything posted on here about updates >>> yesterday, and I was too in the thick of it to add anything just yet. >>> I realize most are not bleeding edge, so just a heads-up that you >>> may have some issues-hopefully this helps someone else and MS can sort it. >>> >>> Of the servers updated yesterday: >>> >>> all but one of our WS12R2 servers halted with a BSOD on restart: >>> >>> Page_fault_in_nonpaged_area Win32k.sys >>> >>> Had to hard shut-down, and they all recovered (thankfully). They all >>> think the updates installed fine. >>> >>> All of the WS12 (non-R2) servers appeared to take an extremely long >>> time, and after they came back, I found they wanted the same updates >>> installed again. Turns out they are rolling back and not installing >>> any of them. >>> >>> After things calmed down and stabalized, I scoured around online a >>> bit and didn't see anything, but it was early. Then I looked at the >>> one >>> WS12R2 server that hadn't crashed with a BSOD, and realized it's a >>> non-domain machine that went straight out to MS for updates. Our >>> network admin had patched that one, and had not chosen to install >>> the optional (not security) update KB2975719, which is a decent >>> sized rollup for 2012R2. >>> >>> Based on that, I also looked at the 2012 non-R2 servers and noticed >>> KB2975331, a similar non-security update rollup for 2012. >>> >>> I went forward testing on a few more systems, and found that I can >>> install successfully if I first install all of the other updates >>> except for either KB2975719 or KB2975331, restart, and then install >>> the that rollup and restart again. That seems to avoid the BSOD and >>> the rollback, and has worked today for all but one of my 2012 non-R2 >>> servers (I'm still trying to figure out why just the rollup won't >>> install on this last one-could be something else). >>> >>> Seems like they may have a logic issue in that these rollup updates >>> should not be installed along with other updates (like when updating >>> to a new version of IE), but they don't force it to do so. >>> >>> There are also some postings coming out now about issues with Win7, >>> so buyer beware: >>> >>> http://tech.slashdot.org/story/14/08/14/1713227/microsoft-black-tues >>> da y-patches-bring-blue-screens-of-death >>> >>> -Bonnie >>> >> >> >> >> >> > > > >
