Did your PC go 'haywire' too?

[Doom9]

Mine started bluescreening at the login prompt after installing the latest batch of MS Security fixes (http://isc.sans.org/diary.html?storyid=3132)
A rollback to "a week ago", followed by a reinstallation of Visual Studio (which still doesn't render XML now), and deinstallation of various softwares I determined I didn't need right now later, the PC at least was usable again - but the constant loss and reconnection to Exchange today at work (plus my colleagues telling me about the same experiences) disagree. I guess I should've upgraded to .NET 3.0 after all.

[foxyshadis]

Mine bluescreened Tuesday night. (First time in months, and it's mostly been the video driver's fault until now.) I didn't connect it until now. According to the event log, it did happen while the autoupdate was running. The other patches applied, but the .net one now won't apply at all, possibly a good thing. All my .net apps still work, at least.

On the other hand, my USB ports were acting up Tuesday and crying "reboot me!" anyway, so it may have been an unfortunate confluence.

[check]

While I haven't had bluescreens, I have had some very peculiar behaviour on my XPPro install after these updates. Browsing through explorer has suddenly become very laggy and double clicking shortcuts introduces a noticeable delay.

That said, as this is entirely unlike your problem I'm more inclined to blame Murphy / huge uptime than any update, but I figured I'd mention this just in case.

[Inventive Software]

Now I'm so glad my computer isn't connected to the net for 3 months! :D

Question is, if Microsoft actually admits that the patch was a bit broken, will they recall it and push a newer one out?

[Sirber]

no problem @home (vista) and @work (xp pro)

[shakey]

I guess I'm luck that windows update doesn't actually work for me, I have to manually find, download and install any patch.

Any clue about which one it is that I should avoid?

edit: The reliability update for intel processors maybe? Sound's a bit suspect to me.

[communist]

Microsoft .NET Patch May Make PCs Go "Haywire" (http://developers.slashdot.org/article.pl?sid=07/07/13/1227225)

Though I havent noticed anything unusual on my box after applying the patch.

[clsid]

Got two random bluescreens on wednesday. Today my usb mouse and keyboard suddenly stopped working and I got a "new usb hardware detected" wizard. Luckily everything works again after a reset. My PC was a bit slow too before the usb weirdness. Seems to be ok now.

[SeeMoreDigital]

The only weird thing I noticed was the reappearance of that useless animated dog when I did a search :eek:

[Soulhunter]

Good I dont care about MS updates... :rolleyes:

[CruNcher]

Good i don't care about .Net :D (Most .Net C# apps are to slow and heavy resource intense do we really wan't all this going back and nobody except MS knows how to programm on a lower level anymore in my eyes (Megui as a good example) - starting time and I/O access for that what the app does are ridicoulus), but there also other examples Sony Vegas is very fast (.Net C++) :D

[Boulder]

That one update refuses to install..and looks like it's a good thing:)

[burfadel]

Should start getting used to Net framework, its still in development and will eventually replace (or intended to) the normal Windows subsystem. There's 3.5 coming out end of the year/early next year. Its a good idea in principal, each application is supposedly automatically optimised for each computer it is running on.

[Dr.Khron]

Wow, I just got my first bluescreen since I built this PC 4 years ago!

I was afraid that I was having some hardware failure, so I'm glad that other people have gotten this. If its an MS patch then there is a chance that they will fix whatever they broke in a later patch.

Luckily, its only happened once so far.

[clsid]

Yesterday I decided to completely uninstall .NET because I had three versions installed (1.0 1.1 and 2.0). Which is probably redundant? Of course the uninstallers didn't work properly, so it took me almost an hour to remove all the leftovers.

Finally I did a clean install of .NET 2.0 plus three patches for it. I ignored the last reboot prompt, to let the .NET processes do their job rebuilding the assemblies without any interruptions. Once completed (see ngen_service.log), I rebooted. All was well the rest of the day.

Today I suddenly got the USB problems again. Plus some nice BSODs the first three reboots.

[SeeMoreDigital]

Yesterday I decided to completely install .NET because I had three versions installed (1.0 1.1 and 2.0). Which is probably redundant? Of course the uninstallers didn't work properly, so it took me almost an hour to remove all the leftovers. That reminds me....

Around a month ago I formatted and re-installed WinXP and decided to install .NET 3.0. When I visited "Add or Remove Programs" I noticed both .NET 2.0 and 3.0 had been installed :eek:

[clsid]

From what I have read:
3.0 is basically just 2.0 plus some additional stuff