Hi Steve,
You have actually already answered your query as to why you are having these
problems. This has been pointed out by several people (myself included) in
several of these newsgroups. DO NOT obtain hardware drivers and updates from
Microsoft for anything other than Microsoft devices - for all other devices,
go directly to the manufacturer's website. Unfortunately, the only way that I
can think of to restore the other machines to their previous condition would
be to reload them.
Dwarf
"Steve Maser" wrote:
> Hi all...
>
> We primarily update our Windows load sets for new hardware by
> installing a load set to new hardware, installing any drivers
> necessary, running Windows Update to install any updates, then
> re-sysprepping the set.
>
> We did a series of hardware updates for the load set recently for 4
> different hardware models (Latitude D530, Sony VGN-SZ340, Dell
> Precision T3400 and Lenovo T61).
>
> From my notes, the drivers (7 from Windows Update!) from the Lenovo
> T61 caused the following problem:
>
> At system startup, the "Microsoft Windows" screen comes up, then
> there's about a 1.5 minute black screen with a white mouse cursor
> (which moves fine), then the Vista logo icon thing, then the normal
> login window.
>
> The 1.5 minute black screen is the newly-added problem after the
> Lenovo driver updates from Windows Update apparently.
>
>
> The Lenovo T61 I had has been passed back on to the user, so I can't
> get my hands on it to track down which of the 7 driver updates might
> have caused this.
>
> Luckily, I am able to revert my load sets back to before the Lenovo
> was added to it, but we passed on this "broken" load set to a couple of
> other models of hardware (like MacBook Pros) before we caught this as
> an issue.
>
>
>
> So, I'm looking for suggestions to how to "fix" the problem on the
> few machines that got the "broken" load set before we noticed this
> problem (short of reloading it)...
>
> Anybody have any suggestions how to figure out what's actually
> happening at the bootup process that would be causing this?
>
> - Steve
>
|