Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   Windows 64bit (http://www.velocityreviews.com/forums/f46-windows-64bit.html)
-   -   x64 will not boot after installing latest MS AntiSpyware (http://www.velocityreviews.com/forums/t488160-x64-will-not-boot-after-installing-latest-ms-antispyware.html)

=?Utf-8?B?TWFyayBIYXJ0dC1QYWxtZXI=?= 06-29-2005 08:51 AM

x64 will not boot after installing latest MS AntiSpyware
 
I received an update notification to inform me that a new build of MS
AntiSpyware was available. I duly downloaded and installed it. The
installation asked for a restart. After the restart, I got the following
message informing me that the \CONFIG\SYSTEM file was missing or corrupt.

I assume that this registry hive is damaged. My question is really to ask
whether the AntiSpyware installation could have caused this corruption, or is
it pure coincidence?

Any help on recovering the registry without having to do a complete
reinstall would be much appreciated. BTW, I have tried to boot from the CD
and do a repair install, but I suspect that the boot.ini file might be
damaged also.

Many thanks

Mark Hartt-Palmer

John Barnes 06-29-2005 11:32 AM

Re: x64 will not boot after installing latest MS AntiSpyware
 
You can fix your boot.ini from the recovery console on your Windows CD.
Select option R and use bootcfg /help at the command prompt a
bootcfg /list will show you what is there and you can select the option
that you want


"Mark Hartt-Palmer" <Mark Hartt-Palmer@discussions.microsoft.com> wrote in
message news:89E78341-71AE-4CBA-AF25-24D570035F7F@microsoft.com...
>I received an update notification to inform me that a new build of MS
> AntiSpyware was available. I duly downloaded and installed it. The
> installation asked for a restart. After the restart, I got the following
> message informing me that the \CONFIG\SYSTEM file was missing or corrupt.
>
> I assume that this registry hive is damaged. My question is really to ask
> whether the AntiSpyware installation could have caused this corruption, or
> is
> it pure coincidence?
>
> Any help on recovering the registry without having to do a complete
> reinstall would be much appreciated. BTW, I have tried to boot from the
> CD
> and do a repair install, but I suspect that the boot.ini file might be
> damaged also.
>
> Many thanks
>
> Mark Hartt-Palmer




Gary MCSE 06-29-2005 12:54 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
I had the same problem and I used the recovery console. The fix was to run
FIXMBR

"John Barnes" <jbfoofy@email.net> wrote in message
news:eNtkE5JfFHA.3436@tk2msftngp13.phx.gbl...
> You can fix your boot.ini from the recovery console on your Windows CD.
> Select option R and use bootcfg /help at the command prompt a
> bootcfg /list will show you what is there and you can select the option
> that you want
>
>
> "Mark Hartt-Palmer" <Mark Hartt-Palmer@discussions.microsoft.com> wrote in
> message news:89E78341-71AE-4CBA-AF25-24D570035F7F@microsoft.com...
>>I received an update notification to inform me that a new build of MS
>> AntiSpyware was available. I duly downloaded and installed it. The
>> installation asked for a restart. After the restart, I got the following
>> message informing me that the \CONFIG\SYSTEM file was missing or corrupt.
>>
>> I assume that this registry hive is damaged. My question is really to
>> ask
>> whether the AntiSpyware installation could have caused this corruption,
>> or is
>> it pure coincidence?
>>
>> Any help on recovering the registry without having to do a complete
>> reinstall would be much appreciated. BTW, I have tried to boot from the
>> CD
>> and do a repair install, but I suspect that the boot.ini file might be
>> damaged also.
>>
>> Many thanks
>>
>> Mark Hartt-Palmer

>
>




=?Utf-8?B?TWFyayBIYXJ0dC1QYWxtZXI=?= 06-29-2005 01:50 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
Many thanks John / Gary. I'll certainly try these methods when I get home
later! I've also printed off the knowledge base article 307545 (How to
recover from a corrupted registry that prevents Windows XP from starting),
but I hope I won't need to refer to this if the other methods work.

Andre Da Costa [Extended64] 06-29-2005 03:03 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
Mark, could you also report this to the
microsoft.private.security.spyware.appcompat and
microsoft.private.security.spyware.general newsgroups, I'm sure the MSAS
Team would love to hear about this. I recommend people do not do the
automatic update or upgrade of MSAS, download it from the site, shutdown
Microsoft AntiSpyware from the notification, uninstall, restart and install
the new build, which is 614.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Mark Hartt-Palmer" <Mark Hartt-Palmer@discussions.microsoft.com> wrote in
message news:89E78341-71AE-4CBA-AF25-24D570035F7F@microsoft.com...
>I received an update notification to inform me that a new build of MS
> AntiSpyware was available. I duly downloaded and installed it. The
> installation asked for a restart. After the restart, I got the following
> message informing me that the \CONFIG\SYSTEM file was missing or corrupt.
>
> I assume that this registry hive is damaged. My question is really to ask
> whether the AntiSpyware installation could have caused this corruption, or
> is
> it pure coincidence?
>
> Any help on recovering the registry without having to do a complete
> reinstall would be much appreciated. BTW, I have tried to boot from the
> CD
> and do a repair install, but I suspect that the boot.ini file might be
> damaged also.
>
> Many thanks
>
> Mark Hartt-Palmer




M. Murcek 06-29-2005 06:03 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
Interesting. I downloaded and installed the latest version of MS
Anti-Spyware right after install of x64 Edition, and it was just fine.
Maybe the upgrade behaves differently?

"Mark Hartt-Palmer" <Mark Hartt-Palmer@discussions.microsoft.com> wrote in
message news:89E78341-71AE-4CBA-AF25-24D570035F7F@microsoft.com...
>I received an update notification to inform me that a new build of MS
> AntiSpyware was available. I duly downloaded and installed it. The
> installation asked for a restart. After the restart, I got the following
> message informing me that the \CONFIG\SYSTEM file was missing or corrupt.
>
> I assume that this registry hive is damaged. My question is really to ask
> whether the AntiSpyware installation could have caused this corruption, or
> is
> it pure coincidence?
>
> Any help on recovering the registry without having to do a complete
> reinstall would be much appreciated. BTW, I have tried to boot from the
> CD
> and do a repair install, but I suspect that the boot.ini file might be
> damaged also.
>
> Many thanks
>
> Mark Hartt-Palmer




Andre Da Costa [Extended64] 06-29-2005 06:51 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
There is also some issue upgrading from definitions 5725 to 5729, here is a
fix for it:
If you know what you are doing :')
Follow this, all credits to user "Taxman":

- Download Winzip or 7-Zip
http://www.7-zip.org/

Download these 3 files, right click-save to disk.
Compressed files !

http://download.spynet.com/ASDefinit...nationData.gcz
http://download.spynet.com/ASDefinit...itScanData.gcz
http://download.spynet.com/ASDefinit...ThreatData.gcz

- Open the first downloaded file and extract it with your Zip tool .
Do the same for the other.

- Right click on MSAS icon and choose shutdown.

- Copy/paste your extracted files to Program files / Microsoft
Antispyware
and choose to overwrite existing definition files.

- Start MSAS again and make a "check for updates" if you have latest
defs.

- If you have time, perform a full system scan directly with all
options checked.

--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"M. Murcek" <mamurcekjr@worldnet.att.net> wrote in message
news:OFcaeRNfFHA.1472@TK2MSFTNGP12.phx.gbl...
> Interesting. I downloaded and installed the latest version of MS
> Anti-Spyware right after install of x64 Edition, and it was just fine.
> Maybe the upgrade behaves differently?
>
> "Mark Hartt-Palmer" <Mark Hartt-Palmer@discussions.microsoft.com> wrote in
> message news:89E78341-71AE-4CBA-AF25-24D570035F7F@microsoft.com...
>>I received an update notification to inform me that a new build of MS
>> AntiSpyware was available. I duly downloaded and installed it. The
>> installation asked for a restart. After the restart, I got the following
>> message informing me that the \CONFIG\SYSTEM file was missing or corrupt.
>>
>> I assume that this registry hive is damaged. My question is really to
>> ask
>> whether the AntiSpyware installation could have caused this corruption,
>> or is
>> it pure coincidence?
>>
>> Any help on recovering the registry without having to do a complete
>> reinstall would be much appreciated. BTW, I have tried to boot from the
>> CD
>> and do a repair install, but I suspect that the boot.ini file might be
>> damaged also.
>>
>> Many thanks
>>
>> Mark Hartt-Palmer

>
>




Charlie Russel - MVP 06-30-2005 06:29 AM

Re: x64 will not boot after installing latest MS AntiSpyware
 
hmmm. Not seeing an issue here...

--
Charlie.
http://www.msmvps.com/xperts64/


Mark Hartt-Palmer wrote:
> I received an update notification to inform me that a new build of MS
> AntiSpyware was available. I duly downloaded and installed it. The
> installation asked for a restart. After the restart, I got the
> following message informing me that the \CONFIG\SYSTEM file was
> missing or corrupt.
>
> I assume that this registry hive is damaged. My question is really
> to ask whether the AntiSpyware installation could have caused this
> corruption, or is it pure coincidence?
>
> Any help on recovering the registry without having to do a complete
> reinstall would be much appreciated. BTW, I have tried to boot from
> the CD and do a repair install, but I suspect that the boot.ini file
> might be damaged also.
>
> Many thanks
>
> Mark Hartt-Palmer




=?Utf-8?B?TWFyayBIYXJ0dC1QYWxtZXI=?= 06-30-2005 08:56 AM

Re: x64 will not boot after installing latest MS AntiSpyware
 
Andre, I will report these to the relevant MS Newsgroups. I think that the
startup problems could have been pure coincidence though. Thankfully, I
managed to fex the problem fairly quickly, by:

1. Booting from the x64 CD and going into the Recovery Console
2. Changing the attributes of the ntldr and boot.ini files so that I could
delete them
3. Copying ntldr and ntdetect from the CD to my hard drive
4. Doing a BootCfg / Rebuild.

Many thanks for the help that was offered.

"Charlie Russel - MVP" wrote:

> hmmm. Not seeing an issue here...
>
> --
> Charlie.
> http://www.msmvps.com/xperts64/
>
>
> Mark Hartt-Palmer wrote:
> > I received an update notification to inform me that a new build of MS
> > AntiSpyware was available. I duly downloaded and installed it. The
> > installation asked for a restart. After the restart, I got the
> > following message informing me that the \CONFIG\SYSTEM file was
> > missing or corrupt.
> >
> > I assume that this registry hive is damaged. My question is really
> > to ask whether the AntiSpyware installation could have caused this
> > corruption, or is it pure coincidence?
> >
> > Any help on recovering the registry without having to do a complete
> > reinstall would be much appreciated. BTW, I have tried to boot from
> > the CD and do a repair install, but I suspect that the boot.ini file
> > might be damaged also.
> >
> > Many thanks
> >
> > Mark Hartt-Palmer

>
>
>


Andre Da Costa [Extended64] 06-30-2005 02:53 PM

Re: x64 will not boot after installing latest MS AntiSpyware
 
Yes, but we don't want people doing this in Microsoft AntiSpywares final
iteration. Its best reporting it to the group to prevent this from happening
in the future to XP Pro x64 users.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Mark Hartt-Palmer" <MarkHarttPalmer@discussions.microsoft.com> wrote in
message news:702C5908-5042-4F03-8A75-A8F57C2B01B3@microsoft.com...
> Andre, I will report these to the relevant MS Newsgroups. I think that
> the
> startup problems could have been pure coincidence though. Thankfully, I
> managed to fex the problem fairly quickly, by:
>
> 1. Booting from the x64 CD and going into the Recovery Console
> 2. Changing the attributes of the ntldr and boot.ini files so that I
> could
> delete them
> 3. Copying ntldr and ntdetect from the CD to my hard drive
> 4. Doing a BootCfg / Rebuild.
>
> Many thanks for the help that was offered.
>
> "Charlie Russel - MVP" wrote:
>
>> hmmm. Not seeing an issue here...
>>
>> --
>> Charlie.
>> http://www.msmvps.com/xperts64/
>>
>>
>> Mark Hartt-Palmer wrote:
>> > I received an update notification to inform me that a new build of MS
>> > AntiSpyware was available. I duly downloaded and installed it. The
>> > installation asked for a restart. After the restart, I got the
>> > following message informing me that the \CONFIG\SYSTEM file was
>> > missing or corrupt.
>> >
>> > I assume that this registry hive is damaged. My question is really
>> > to ask whether the AntiSpyware installation could have caused this
>> > corruption, or is it pure coincidence?
>> >
>> > Any help on recovering the registry without having to do a complete
>> > reinstall would be much appreciated. BTW, I have tried to boot from
>> > the CD and do a repair install, but I suspect that the boot.ini file
>> > might be damaged also.
>> >
>> > Many thanks
>> >
>> > Mark Hartt-Palmer

>>
>>
>>





All times are GMT. The time now is 04:29 PM.

Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57