Vista B2 - Recovery Console?


Upgrade a machine to Vista Beta 2 - system hangs and reboots right during/after agp440.sys - I know a few days to troubleshoot this but in Vista there seems to be no Recovery Console - just a command prompt under "recovery options"

How does one disable a service when there is no listsvc command, and mmc won't start?

thanks in advance!
Dan FloodDeveloperAsked:
Who is Participating?
windows_eXPertConnect With a Mentor Commented:
Wonderful. I'd try to replace it off the cd.
Unfortunately, Vista is still beta, so it's likely that this is just a beta thing that really can't be fixed. You might just have to format it.
Hi jakyll,
Take a look here: and see if that helps.
Good Luck,
Can you boot to safemode? Try booting from the CD, going to console, and replacing the agp440.sys with a copy from the cd. Sorry for the generic responses, but I am away from my Vista box...

What service is it part of?
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Dan FloodDeveloperAuthor Commented:
I am not sure actually - the system gets to AGP440.SYS and then BSOD's with a 7E error....  Not even safemode will work.
Vista should be installed on a naked machine.  Trying to have two Operating Systems or upgrading to Vista, and beta, is generally going to fail somewhere along the line.

Vistat beta 2 should be tested on a standalone machine.


Hardly any drivers have been written for the 64-bit oriented software and it is far from being stable.
I concur, although I have XP, Vista, and Dapper on the same PC. However, I've never run an upgrade; I've always done a secondary (dual-boot) install. However, both (oldos and Vista) are fucked up now. Try doing a clean install, and see if it is a hardware problem, or just crazy #hit associated with beta and upgrading. To dual-boot XP and Vista:

1. Boot the XP cd. Make a partition half the size (or whatever you want the vista size is) of the disk, and make another one the rest of the drive. Install XP on the *second* one.
2. Boot from Vista, install to the first. Should work from there.

It doesn't look as if you will be able to save the installs. That's the price of being on the bleeding/cutting edge. Sorry...
I have yet to experience anything 'unstable' about Vista.
I loaded it on top of an old XP Pro load and it has been behaving perfectly.

Software 64 Bit drivers are no big deal - because Vista was designed to run 'older' software interchangably.
Most of my hardware drivers are 64 bit and there have been no problems with that either.
I know it *usually* works fine, but it has a larger proportion of bugs than other MS software for a couple of reasons:

1. It was completely rewritten, introducing new and unnoticed bugs. There has simply been less time for them to show themselves, as opposed to XP which has had bugs discovered (and removed) through at least 3 major versions, and several more minor ones.
2. It has probably not been tested on kinky/strange environments, at least not much. So, there is less chance for one to show up.
3. It's still being fixed.
If history has any value, we will probably see lots of 'undocumented features' in Vista, just as we have in all the other MS products.
I am not a cock-eyed optimist, but so far, so good.
I am still keeping one pure XP Pro box running as I play with the Vista box.
For us, XP has been an incredibly stable platform - especially after the problems with NT and WIN2K.
"Software 64 Bit drivers are no big deal "


Secondly, Vista's big push is that it is the first All 64-bit Operating System.

About the stability, "where have I heard that before???"  (2.)  XP IS NT and Windows 2000; stability evolved over about four different names, and nearly 10 years now.

My bet is more discussion and error questions on Vista than all other Windows Operating Systems combined, even here on Experts Exchange.

It's late coming out because everyone had to go back to school to learn 64-bit architecture; school is far from over!

Probelm A.)  We found that Vista could not understand it's own variable names, as in %SystemRoot% being equal to any other drive than the C drive, and therefore, when we installed it on D drive, it was accessing everything in the old XP Operating System on the C drive; obviously, this is not good.

You wouldn't see that problem until it was too late, i.e., Vista overwrote critical files in %SystemRoot% hybriding and totally corrupting the XP Operating System and that would not be evident until the system crashed, which would crash both Operating Systems; a complete system failure and permanent Blue Screen of Death.

No, it's not stable yet, far from it.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.