Microsoft: Please Avoid Security Update KB2823324

[Johnny]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

 

[Kirk Bubul]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

I'm running 64-bit Windows 7 SP1 and this patch caused me to go
into the CHKDSK upon booting the next morning. I then read about
the problems with this patch and used Control Panel Uninstall to
remove this patch.

All became well again.

 

[Dave-UK]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

I had it installed on 10 April 2013 and have had no problems, 32 bit Win7.

 

[Johnny]

I had it installed on 10 April 2013 and have had no problems, 32 bit Win7.

I haven't had a problem with it either.

Under Update Settings in Control Panel, I have download updates, but let
me decide whether or not to install them. Then when I shutdown the
computer, I get the message that Windows is installing updates, do not
turn the computer off.

I will change the setting to never check for updates, and see how that
works.

 

[Scott]

I haven't had a problem with it either.

Under Update Settings in Control Panel, I have download updates, but let
me decide whether or not to install them. Then when I shutdown the
computer, I get the message that Windows is installing updates, do not
turn the computer off.

Out of interest, what criteria do you apply to in your decision-making
process?

I will change the setting to never check for updates, and see how that
works.

Your computer probably won't get updated!

 

[Johnny]

Out of interest, what criteria do you apply to in your decision-making
process?
Your computer probably won't get updated!

It will get updated, about a week after Microsoft sends out the updates.
Then I can choose not to install an update if there is a problem with it.

 

[Scott]

It will get updated, about a week after Microsoft sends out the updates.
Then I can choose not to install an update if there is a problem with it.

But what criteria do you apply in your decision-making process?

 

[sticks]

It isn't called exploit Wednesday for nothing.

On second thinking about this, I kinda like this strategy. Wait about a
week for everyone else to test out the updates, and then go ahead and do
your own system. Makes sense.

 

[chicagofan]

On second thinking about this, I kinda like this strategy. Wait about
a week for everyone else to test out the updates, and then go ahead
and do your own system. Makes sense.

That's what I do, after checking the Security forum at BBR to see what
complaints have been registered about specific updates. I've been doing
that since a MS update knocked out the sound on videos at some sites
[i.e.youtube, news sites]earlier this year for me.

Had I been reading that forum before that happened I could have avoided
uninstalling, etc.. In both cases, MS came along later and changed
those updates from important to optional.
bj

 

[webster72n]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

Just for informational purposes I would like to mention that I did not
have any problems whatsoever downloading and installing the updates,
including the one you pointed out.
My OS: WinVista, Home Premium SP2 and IE9.
Apparently this is a Win7-specific situation.

Harry.

 

[Bob H]

I had it installed on 10 April 2013 and have had no problems, 32 bit Win7.

It was installed on my win 7 64 bit system on 12th April, and I've not
had any problems either

 

[Drew]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

Kind of weird but I noticed that I had this update installed on my win 7
64 bit pro machine and my wife's win 7 64 bit prem machine. Ever since
it was installed on the 12th IE9 has been slower than crap and that was
really the only noticeable problem with it. Once uninstalled things are
back to normal. As I said, weird!

 

[Paul]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

Wait until a root cause analysis has been done ?

http://blogs.technet.com/b/msrc/arc...o-address-security-bulletin-update-issue.aspx

"update 2823324 ...which we provided in security bulletin MS13-036
on Tuesday, April 9. We’ve determined that the update, when paired
with certain third-party software, can cause system errors."

In one forum, someone mentioned ntfs.sys, so the problem
could have some relation to the file system. And if they're
fooling around with that (Microsoft), then it was probably
done to block malware of some kind. (Root kits like to hide,
by attacking some layer of the file system.)

It's too bad they didn't name the third-party software. It
could be an AV for example. Or any tool that happens to
shim the ntfs driver or something. We'll probably need an
MSVP to leak the appropriate info (name names). I think
it's good to know the root cause, just for future reference
when something else breaks.

Paul

 

[s|b]

It was installed on my win 7 64 bit system on 12th April, and I've not
had any problems either

Same here. W7 HP x64 SP1, all updates installed, no problems.

 

[Paul]

Wait until a root cause analysis has been done ?

http://blogs.technet.com/b/msrc/arc...o-address-security-bulletin-update-issue.aspx


"update 2823324 ...which we provided in security bulletin MS13-036
on Tuesday, April 9. We’ve determined that the update, when paired
with certain third-party software, can cause system errors."

In one forum, someone mentioned ntfs.sys, so the problem
could have some relation to the file system. And if they're
fooling around with that (Microsoft), then it was probably
done to block malware of some kind. (Root kits like to hide,
by attacking some layer of the file system.)

It's too bad they didn't name the third-party software. It
could be an AV for example. Or any tool that happens to
shim the ntfs driver or something. We'll probably need an
MSVP to leak the appropriate info (name names). I think
it's good to know the root cause, just for future reference
when something else breaks.

Paul

http://securitywatch.pcmag.com/soft...-yanks-faulty-update-from-april-patch-tuesday

"The bulletin can cause system errors on systems running
"certain third-party software," Childs said.

Qualys CTO Wolfgang Kandek identified the software as a
banking security plugin called "G-Buster," which provides a
virtualized environment for safer online banking.

"G-Buster is interfering with the Windows kernel patch," Kandek said.
"

So if you scout around, info about it is leaking.

Paul

 

[Paul in Houston TX]

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the
32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

I always use manual updates so went to the MS up site and
2823324 did not show up on the list of recommended updates.
It must have been removed from MS, per the article.

 

[Paul]

http://securitywatch.pcmag.com/soft...-yanks-faulty-update-from-april-patch-tuesday


"The bulletin can cause system errors on systems running
"certain third-party software," Childs said.

Qualys CTO Wolfgang Kandek identified the software as a
banking security plugin called "G-Buster," which provides a
virtualized environment for safer online banking.

"G-Buster is interfering with the Windows kernel patch," Kandek said.
"

So if you scout around, info about it is leaking.

Paul

And KAV is also implicated, because they released a patch themselves.
And KAV is probably interested in things like ntfs.sys. Or any part
of the file system, that needs malware protection.

http://news.softpedia.com/news/Kasp...Buggy-Microsoft-KB2823324-Update-345161.shtml

Paul

 

[s|b]

On second thinking about this, I kinda like this strategy. Wait about a
week for everyone else to test out the updates, and then go ahead and do
your own system. Makes sense.

I make a backup image (and make an extra copy to an external hdd) before
I install Windows Updates. To me, this makes more sense than waiting it
out for a week.

 

[...winston]

It's not impacting everyone. Thought to be also related to the presence of specific software and hardware.

A successful installation of the update doesn't negate the fact that the update (installed, hidden, or removed) is the cause of the
problem.



--
....winston
msft mvp consumer apps


"Dave-UK" wrote in message

By Kevin Parrish April 12, 2013 11:20 AM - Source: Winbeta


A security update distributed in April 2013 Patch Tuesday may put the 32-bit version of Windows 7 in an infinite boot loop.

http://www.tomshardware.com/news/KB...Patch-Tuesday-Infinite-Reboot-Loop,22016.html

I had it installed on 10 April 2013 and have had no problems, 32 bit Win7.

 

[Gene E. Bloch]

It's not impacting everyone. Thought to be also related to the presence of specific software and hardware.

A successful installation of the update doesn't negate the fact that the update (installed, hidden, or removed) is the cause of the
problem.

True (i.e., valid logic), but at the same time, the fact that "you" had
a problem doesn't (necessarily) mean that "I" should avoid it - for
various values of "you" and "I".

But those using caution are smarter than I was when I installed it

Luckily, I was one of the lucky ones.