It seems Windows update killed my new computer

[Dan Burk]

On April 29th I put my new computer online . It's a P4
2.67 Ghz model with Intel motherboard, running WIndows XP
Pro SP1. It's ten days old, with only one installed
aftermarket software package (which was not running at the
time). Up pops a Windows update message which I authorize.
After several minutes of downloads, the update tool
prompts for a system restart to enable the changes.
Instead of restarting, the screen goes black and the
following message pops up:

"NTLDR is missing. Press any key to continue"

Pressing any key yields no other result.

Since the computer store refuses to warranty software
(especially operating systems) and Microsoft seems to want
the computer manufacturer to take care of service, it
seems I am caught with no warranty support. Can anyone
help shed some insight on a procedure I can use to bring
my system back to life?

[D.Currie]

"Dan Burk" > wrote in message
...
> On April 29th I put my new computer online . It's a P4
> 2.67 Ghz model with Intel motherboard, running WIndows XP
> Pro SP1. It's ten days old, with only one installed
> aftermarket software package (which was not running at the
> time). Up pops a Windows update message which I authorize.
> After several minutes of downloads, the update tool
> prompts for a system restart to enable the changes.
> Instead of restarting, the screen goes black and the
> following message pops up:
>
> "NTLDR is missing. Press any key to continue"
>
> Pressing any key yields no other result.
>
> Since the computer store refuses to warranty software
> (especially operating systems) and Microsoft seems to want
> the computer manufacturer to take care of service, it
> seems I am caught with no warranty support. Can anyone
> help shed some insight on a procedure I can use to bring
> my system back to life?

Part of the OEM agreement is that the system builder/reseller of the OEM
software is required to support the product, which is one reason why OEM
software is cheaper than retail. Basically, the reseller gets it for less
because Microsoft isn't adding in their cost of support.

So if it's OEM software, MS won't give you support without paying a fee.

If the reseller won't provide you with the contracted support, they're
pretty much cheating you.

You could return the computer and ask for a refund, then go buy one that
works and has support.

You could also try reloading Windows from whatever CDs they gave you. But if
it's that new and you're having these sorts of problems already, I'd
question the reliability of the system overall.

[Dan Burk]

Very good point. I've already told them that I was quite
disappointed with their attitude. I dont plan on returning.

However, it looks as if I was able to figure out the
problem myself this time. After doing a repair/ reinstall
from the installation CD, the error was still there. It
was then that I noticed, much to my embarrassment, that
there was a floppy disc in the flopp drive. When I removed
the disc, the problem disappeared.

Thus, even though the knowledge base does not say so, a
solution to this type of error may be embarrasingly
simple: Check your boot sequence in BIOS, and see if a
blank floppy in the disc drive gets boot priority over
those perfectly good system files on the hard drive.


>-----Original Message-----
>
>"Dan Burk" > wrote in message
...
>> On April 29th I put my new computer online . It's a P4
>> 2.67 Ghz model with Intel motherboard, running WIndows
XP
>> Pro SP1. It's ten days old, with only one installed
>> aftermarket software package (which was not running at
the
>> time). Up pops a Windows update message which I
authorize.
>> After several minutes of downloads, the update tool
>> prompts for a system restart to enable the changes.
>> Instead of restarting, the screen goes black and the
>> following message pops up:
>>
>> "NTLDR is missing. Press any key to continue"
>>
>> Pressing any key yields no other result.
>>
>> Since the computer store refuses to warranty software
>> (especially operating systems) and Microsoft seems to
want
>> the computer manufacturer to take care of service, it
>> seems I am caught with no warranty support. Can anyone
>> help shed some insight on a procedure I can use to bring
>> my system back to life?
>
>Part of the OEM agreement is that the system
builder/reseller of the OEM
>software is required to support the product, which is one
reason why OEM
>software is cheaper than retail. Basically, the reseller
gets it for less
>because Microsoft isn't adding in their cost of support.
>
>So if it's OEM software, MS won't give you support
without paying a fee.
>
>If the reseller won't provide you with the contracted
support, they're
>pretty much cheating you.
>
>You could return the computer and ask for a refund, then
go buy one that
>works and has support.
>
>You could also try reloading Windows from whatever CDs
they gave you. But if
>it's that new and you're having these sorts of problems
already, I'd
>question the reliability of the system overall.
>
>
>.
>

[D.Currie]

Funny how something that simple can mess things up.

At least it wasn't a fatal error. :)

"Dan Burk" > wrote in message
...
> Very good point. I've already told them that I was quite
> disappointed with their attitude. I dont plan on returning.
>
> However, it looks as if I was able to figure out the
> problem myself this time. After doing a repair/ reinstall
> from the installation CD, the error was still there. It
> was then that I noticed, much to my embarrassment, that
> there was a floppy disc in the flopp drive. When I removed
> the disc, the problem disappeared.
>
> Thus, even though the knowledge base does not say so, a
> solution to this type of error may be embarrasingly
> simple: Check your boot sequence in BIOS, and see if a
> blank floppy in the disc drive gets boot priority over
> those perfectly good system files on the hard drive.
>
>
> >-----Original Message-----
> >
> >"Dan Burk" > wrote in message
> ...
> >> On April 29th I put my new computer online . It's a P4
> >> 2.67 Ghz model with Intel motherboard, running WIndows
> XP
> >> Pro SP1. It's ten days old, with only one installed
> >> aftermarket software package (which was not running at
> the
> >> time). Up pops a Windows update message which I
> authorize.
> >> After several minutes of downloads, the update tool
> >> prompts for a system restart to enable the changes.
> >> Instead of restarting, the screen goes black and the
> >> following message pops up:
> >>
> >> "NTLDR is missing. Press any key to continue"
> >>
> >> Pressing any key yields no other result.
> >>
> >> Since the computer store refuses to warranty software
> >> (especially operating systems) and Microsoft seems to
> want
> >> the computer manufacturer to take care of service, it
> >> seems I am caught with no warranty support. Can anyone
> >> help shed some insight on a procedure I can use to bring
> >> my system back to life?
> >
> >Part of the OEM agreement is that the system
> builder/reseller of the OEM
> >software is required to support the product, which is one
> reason why OEM
> >software is cheaper than retail. Basically, the reseller
> gets it for less
> >because Microsoft isn't adding in their cost of support.
> >
> >So if it's OEM software, MS won't give you support
> without paying a fee.
> >
> >If the reseller won't provide you with the contracted
> support, they're
> >pretty much cheating you.
> >
> >You could return the computer and ask for a refund, then
> go buy one that
> >works and has support.
> >
> >You could also try reloading Windows from whatever CDs
> they gave you. But if
> >it's that new and you're having these sorts of problems
> already, I'd
> >question the reliability of the system overall.
> >
> >
> >.
> >