Microsoft, you have a BUG in one of your patches

[SepticTank]

This has been going on for more than 2 months.

Here is the deal: I run a computer shop and we often have to do
reloads to computers due to spyware and viruses eating them up.

Reloading Windows XP with ALL the updates will result in a
"SVCHOST.EXE has caused an errort" on boot up *IF* there is no network
connection present.

We reload our systems via broadband. Every machine works fine, but as
soon as you unplug the RJ45 cable, the system will 90% of the time
boot up with that error.

This has happen to many systems across a couple of months now. Let me
re-itterate: These are freshly loaded PCs with NO viruses, NO spyware.
I've even verified this error at home with my own PC (and my own ISP),
so I know it's nothing to do with our environment.

The only workaround I've found is to not do any updates. I'll reload
the systems with an XP SP2 disc, but turn off automatic updates. I
get no errors when none of the patches have been installed post SP2.

Also, the error appears to be related to the automatic update service.
if I turn it off completely, the error occurs much less frequently,
but will still pop up on the occasional boot-up.

 

[Haggis]

This has been going on for more than 2 months.

Here is the deal: I run a computer shop and we often have to do
reloads to computers due to spyware and viruses eating them up.

Reloading Windows XP with ALL the updates will result in a
"SVCHOST.EXE has caused an errort" on boot up *IF* there is no network
connection present.

We reload our systems via broadband. Every machine works fine, but as
soon as you unplug the RJ45 cable, the system will 90% of the time
boot up with that error.

This has happen to many systems across a couple of months now. Let me
re-itterate: These are freshly loaded PCs with NO viruses, NO spyware.
I've even verified this error at home with my own PC (and my own ISP),
so I know it's nothing to do with our environment.

The only workaround I've found is to not do any updates. I'll reload
the systems with an XP SP2 disc, but turn off automatic updates. I
get no errors when none of the patches have been installed post SP2.

Also, the error appears to be related to the automatic update service.
if I turn it off completely, the error occurs much less frequently,
but will still pop up on the occasional boot-up.

I think your problem is a result of reloading from broadband ....because it
remembers where it loaded from and will always try to verify the install
location...you install from broadband ...it looks for that source when it
boots.

reload from a slipstreamed CD and I bet you won't see that error.

BTW I don think anyone here actually works for MS

 

[SepticTank]

Say what? Slipstreamed CD? Never heard of that. Is that downloading
the individual patches seperately and just placing them on a CD to
execute? Too much work, the MS Update should do the job and not
create errors in the process.

Thanks for the reply.

 

[Pop]

1. This is not the Microsoft COMPANY. This is simply a newsgroup which
volunteers participate on, supported with some help from MS as in passing
tests to become an MVP and so on, but it is NOT a microsoft company site.
You do not talk to Microsoft here. There IS an address for what you want to
say, but I don't know it and can't find it at the moment.

2. Your assessment of the problem ("bug"), IMO, is incorrect. I couldn't
follow part of it, but it would appear to be your methodology is the problem
as opposed to a bug. I admit though, that those might be famous last words!
<g>.
Look a little closer at your processes; that's most likely where the
problem lies.

Regards,

Pop (NOT an MVP, just a happy puter-er).

 

[SepticTank]

Sorry, for some reason I thought that there was limited MS support
here.

I will freely admit that there may be something I'm doing that is
causing the problem, but I don't see what. What could I possibly be
doing wrong by running "Windows Update" until there is no critical
updates left? I mean, I'm doing nothing more than that.

 

[kurttrail]

Say what? Slipstreamed CD? Never heard of that. Is that downloading
the individual patches seperately and just placing them on a CD to
execute? Too much work, the MS Update should do the job and not
create errors in the process.

Thanks for the reply.

Then download the patches to a memory stick or CD, and setup the
computer with no internet connection. Keeping the patches locally would
actually speed up the overall setup process, unless you have a broadband
connection that is faster than USB or CD.

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[kurttrail]

Sorry, for some reason I thought that there was limited MS support
here.

This is a peer to peer support group.

I will freely admit that there may be something I'm doing that is
causing the problem, but I don't see what. What could I possibly be
doing wrong by running "Windows Update" until there is no critical
updates left? I mean, I'm doing nothing more than that.

Basically it sounds to me like you are setting up the computers with a
broadband connection enabled during the install process, and then
getting errors after unplugging the connection. I'd setup the computers
without the broadband connection attached.




--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"

 

[Haggis]

Sorry, for some reason I thought that there was limited MS support
here.

I will freely admit that there may be something I'm doing that is
causing the problem, but I don't see what. What could I possibly be
doing wrong by running "Windows Update" until there is no critical
updates left? I mean, I'm doing nothing more than that.

"windows update " should not cause such a problem...

when you say "reload" do you mean the OS? ...just the updates? it may help
to have the full SP2 on hand locally to install then get the rest of the
updates via broadband

if you stay in this forum long enough , you will see there are some very
knowledgeable people here...it just may take some time to get the answer you
require with the heavy traffic here

 

[SepticTank]

This is what I mean by reload:

1) Boot computer with Windows XP SP2 OEM disc
2) Delete the partition
3) reboot (by pressing F3 to exit!)
4) Boot computer with Wndows XP SP2 OEM disc
5) Install Windows XP SP2
6) Load network drivers if necessary
7) Run Windows Update repeatidly until 0 critical updates are left

Rebooting system with the network cable detached will result in the
error I'm describing.

 

[Steve N.]

This has been going on for more than 2 months.

Here is the deal: I run a computer shop and we often have to do
reloads to computers due to spyware and viruses eating them up.

Reloading Windows XP with ALL the updates will result in a
"SVCHOST.EXE has caused an errort" on boot up *IF* there is no network
connection present.

We reload our systems via broadband. Every machine works fine, but as
soon as you unplug the RJ45 cable, the system will 90% of the time
boot up with that error.

This has happen to many systems across a couple of months now. Let me
re-itterate: These are freshly loaded PCs with NO viruses, NO spyware.
I've even verified this error at home with my own PC (and my own ISP),
so I know it's nothing to do with our environment.

The only workaround I've found is to not do any updates. I'll reload
the systems with an XP SP2 disc, but turn off automatic updates. I
get no errors when none of the patches have been installed post SP2.

Also, the error appears to be related to the automatic update service.
if I turn it off completely, the error occurs much less frequently,
but will still pop up on the occasional boot-up.

I would suspect a hardware driver update. It is generally advised to not
insall driver updates from MS but get them from the hardware
manufacturers instead.

Steve

 

[SepticTank]

I don't use the MS driver updates. I only do the *critical* updates
(top update list).

 

[Haggis]

This is what I mean by reload:

1) Boot computer with Windows XP SP2 OEM disc
2) Delete the partition
3) reboot (by pressing F3 to exit!)
4) Boot computer with Wndows XP SP2 OEM disc
5) Install Windows XP SP2
6) Load network drivers if necessary
7) Run Windows Update repeatidly until 0 critical updates are left

Rebooting system with the network cable detached will result in the
error I'm describing.

do you load "any" other software in this process? ( i follow that general
route myself)

there seems to be alot of discussion about these type of errors , but mainly
on W2000 (guess XP applies too :> )

firewall ?antivirus? proper NIC drivers installed ?

 

[SepticTank]

Nope. The only thing I may load are NIC drivers if XP doesn't have
them out-of-the-box.

Like I said, ths is a totally fresh XP SP2 install on a blank hard
drive. The only thing that I'm loading outside possible NIC drivers
are the critcal updates. And the error will occur.

This is easy to test for any of you. If you're running XP2 SP2,
updated all critical udpates, and have automatic updates turned on,
just unplug your system from your network/cable/DSL modem and reboot
the system a few times. The error should appear.

 

[Leythos]

Reloading Windows XP with ALL the updates will result in a "SVCHOST.EXE
has caused an errort" on boot up *IF* there is no network connection
present.

I run many computers, fully updated/patched, without a network connection
many times during the week - my laptop is only one of those.

 

[Peter Foldes]

Just curious. Have you done a Search for svchost. Do you by any chance have
more that 1 copy running

 

[Ron Martell]

Say what? Slipstreamed CD? Never heard of that. Is that downloading
the individual patches seperately and just placing them on a CD to
execute? Too much work, the MS Update should do the job and not
create errors in the process.

Thanks for the reply.

XP Slipstream:
http://www.winsupersite.com/showcase/windowsxp_sp2_slipstream.asp
http://www.helpwithwindows.com/WindowsXP/winxp-sp2-bootcd.html
http://www.msfn.org/articles.php?action=show&showarticle=49

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

 

[Steve N.]

Just curious. Have you done a Search for svchost. Do you by any chance have
more that 1 copy running

More than one instance of svchost.exe active is not unusual at all and
doesn't indicate anything in and of itself.

Steve

 

[R. McCarty]

To view the actual components running from with an instance of
SvcHost - Start, Run (type) Command [Press Enter] click into
the Command Prompt window and type Tasklist /SVC.
The default Command Prompt window size will not show all the
entries that will scroll by. So before invoking the command best
to maximize the CP window.

 

[Steve N.]

To view the actual components running from with an instance of
SvcHost - Start, Run (type) Command [Press Enter] click into
the Command Prompt window and type Tasklist /SVC.
The default Command Prompt window size will not show all the
entries that will scroll by. So before invoking the command best
to maximize the CP window.

Or scroll up in the CMD box. Good info though, thanks R.

Steve

 

[John [MSFT]]

The next time you see this error, look to see if it offers to send the crash
info to Microsoft. If so, let it send, and then follow the link to see
whether there is any relevant information. The cause of this type of crash
can be lots of different reasons (as you might have surmised from the
various replies on this thread), and while it may be commonly repro'd by
your systems, it doesn't sound like everyone is seeing the same thing. The
crash reporting system uses a sophisticated analysis system to identify
specific issues, and many of them have a fix or workaround available, or
provide other useful info.