negative unintended consequences from Vista Updates ..recommend co

  • Thread starter Thread starter nweissma
  • Start date Start date
N

nweissma

how can i derive the benefit from Vista updates that have negative unintended
consequences?

The latest Vista update was causing my KEYBOARD to abruptly lose power;
after needing to reboot several times, i simply reverted to a past restore
point.

My Vista has been configured for auto updates for nearly 1 year and i have
always had an excellent experience from them. MS Bashers can rampage all they
liike -- MS stays with its customers and is always improving its software.
This is my first negative experience with their updates.

So, how can i install this *important* update? I have since changed from
auto update to manual, but the dilemma persists: when presented with the
option to update, what should i do?
 
Hi nweissa,
I have several Intel chipset based systems that after the updates from
2/12/2008 were applied had various hardware devices stop functioning
completely. Mainly keyboard and mice.

What I discovered was the update forced some devices in the device manager
to be re-initialized and left in a disabled state. By re-enabling them in
the device manager, then rebooting restored proper function with the updates.

I hope your problem is the same as it had me looking all over the event logs
and everywhere with no hint of the the issue. After finding the disabled
devices in the device manager, I was able to successfully use the newest
updates with no other issues.

Good luck and hope this helps!
 
Sometimes it only requires reinstalling the affected driver after the update
has been installed.

I ran into something similar with an XP update affecting the keyboard
driver. System files were altered in such a way that parts of the KB driver
stopped working. In this case a patch was released shortly after the problem
was discovered and all went back to normal. I imagine the solution in your
case depends on where the problem originates.. is it solely the MS update
that causes it, or was something never quite to spec in the keyboard driver,
or is it something specific to just your particular computer. In the first
two cases pretty much everyone with your PC and keyboard would have the
problem and you'd expect a fix to be released pretty quick. Report the
problem to MS and your PC OEM, uninstall the update and wait for the fix or
replace the keyboard and run with the update. If it's just your machine or a
handful of others that have this problem you could be on your own, unless
someone else has figured out a solution.
 
--
32-Vista Home Premium
Intel DG965RY Motherboard
Intel E6400 Processor
OEM = Velocity Micro (Richmond VA)



Confuzzled said:
Hi nweissa,
I have several Intel chipset based systems that after the updates from
2/12/2008 were applied had various hardware devices stop functioning
completely. Mainly keyboard and mice.

What I discovered was the update forced some devices in the device manager
to be re-initialized and left in a disabled state. By re-enabling them in
the device manager,
Click to expand...

HOW DOES ONE RE-ENABLE IN THE DEVICE MANAGER?
 
HOW DOES ONE RE-ENABLE IN THE DEVICE MANAGER?

I'm assuming your mouse does work. If so:
1) Right-Click on My Computer on the Start Menu or Desktop (if you have
chosen to show My Computer on the desktop)
2) Select "Manage" from the right-click menu.
3) On the computer management setup that comes, click on "Device Manager" on
the left side panel.
4) View the list of hardware groups down the middle of the screen. Disabled
devices will already be expanded.
5) Right click on any device that appears disabled on this list and select
"Enable"

This should restore function if your issue is the same as I've encountered
on many PC's here.

Also, I'd recommend restarting your computer so any 3rd party software
associated with these devices may find/initialize the re-enabled device. For
example, if you have a Logitech, Kensington or Microsoft keyboard, many of
these have a systray application for advanced usages. These systray
applications may not immediately recognize the newly enabled device until you
restart your computer. The keyboard should work immediately after enabling
the device though.

Good luck!
 
Back
Top