Vista entering reduced functionality mode without warning

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I received a free copy of Vista Business through the "Power of Together"
promotion.

As I'm currently evaluating whether or not Vista is going to fit my needs I
haven't yet activated the copy. I'm currently try to find a permanent
solution to an issue where Vista appears to go into something that I can only
describe as partial reduced functionality mode after every reboot. The
control panel in the start menu shows as empty, attempting to open the
control panel causes the window to appear briefly and then close. Other
features like the Windows Welcome Center show similar behavior either not
opening at all (with the mouse cursor switching to the circular activity
animation) or the window opening and the closing immediately.

I spent many hours troubleshooting thinking this was potentially a
hardware/driver issue until I eventually discovered people complaining of the
same issue and that what I was facing was in fact Vista going into reduced
functionality mode without telling me. The current work-around for the issue
is stopping and restarting the Software License service after a reboot but
obviously that isn't a permanent solution.

I've reinstalled Vista several times and I can't isolate anything in
particular that would be causing this issue. Does anyone have any
suggestions on how to resolve this?

Regards,

Shelby Cain
 
Shelby--

There are ways to renew the 30 day period, but I suspect you're beyond that.
We've posted them many times on this and the general group. Your post isn't
clear and I'll tell you why.

You say you have a legit Vista sitting on the shelf you acquired from the PT
offer. You obviously are complaining about a Vista setup on that box that
has gone into reduced functionality mode and ironically, you're trying to
evaluate whether to use the Power Together Vista that is legit by using
what?

Vista what edition from where Shelby? You ID it as "I'm currently try to
find a permanent
solution to an issue where Vista appears to go into something that I can
only
describe as partial reduced functionality mode after every reboot:

So if that is an issue for you, it has to do with what you have on the box
and what product key you put in or how you activated it.

To me this doesn't make sense. You have a non-working Vista on the box that
you think is in reduced functionality mode (meaning you can do next to
nothing with it). Why not put in that PT Biz and format and install it.
Evaluate Vista by using Vista. You don't make mention of XP on that
particular box.

1) Shelby is using a Beta?
2) Shelby has a non-legit copy that went into reduced functionality mode?

I'd like to help but I need a post that tells me what's really going on
Shelby.

Vista legit doesn't go into reduced functionality mode lol "without telling
you." And no offense but if you have a Vista that is going to go into
reduced functionality mode--how precisely would it "tell you?"--Warning
message? Some people that use pirated Vista get warnings or when they load
them without a PK they get countdown warnings that could be extended by a
command.

Why are you futzing with whatever Vista you have on the box when you could
get a nicely running Vista by installing the one you have sitting on your
desk? What I can't wait to find out is what in the world kind of Vista did
you spend hours trying to troubleshoot? Does this Vista have a DVD attached
to it. If it does, try to do a startup repair on it. Just search this group
or the general group with the word "boot."

If I missed your point let me know. But your post cries out for what Vista
you have that you're struggling with you think is in reduced functionality
mode, and why you don't just pop in that new Vista waiting for an installt
hat we know is good.

If you think that there are a known percent of Vista legits that go into
reduced functionailty mode, it's a problem I feared would happen given the
erratic WGA performance for a year before Vista RTM'd but hasn't been
reported widely on the web.

Good luck,

CH
 
Shelby--

Are you in any of these categories? Because if you're presenting a legit
Vista including its product key that has gone into reduced functionality
that you have activated that would be interesting. If I had that case, I'd
call MSFT Activation. Or are you misnaming a situation as reduced
functionality that isn't reduced functionality but is a broken Vista that
can be fixed via Startup Repair accessed from the Vista DVD?

The behavior of reduced functionality mode in Windows Vista
http://support.microsoft.com/kb/925582/en-us


CH
 
Chad Harris said:
Shelby--

There are ways to renew the 30 day period, but I suspect you're beyond that.
We've posted them many times on this and the general group. Your post isn't
clear and I'll tell you why.

Your assumption is incorrect. I'm currently 3 days into a _clean_ install
(the _third_ one) on a system I built a week ago. I've haven't attempted to
activate my copy of Vista because of the problem I'm experiencing.
You say you have a legit Vista sitting on the shelf you acquired from the PT
offer. You obviously are complaining about a Vista setup on that box that
has gone into reduced functionality mode and ironically, you're trying to
evaluate whether to use the Power Together Vista that is legit by using
what?

I'm evaluating whether Vista (Business edition obviously as that was the
version the PT promo gave out) is going to be problematic (more specifically
if driver support is problematic) or not on my hardware or if I should
purchase an oem version of XP instead. Obviously, I'd like to save money if
possible but I don't want to waste this license of Vista by activating it on
my system if Vista isn't going to run well. So far, the issue I'm
experiencing is a deal-breaker unless a solution for my problem becomes
apparent.
So if that is an issue for you, it has to do with what you have on the box
and what product key you put in or how you activated it.

To me this doesn't make sense. You have a non-working Vista on the box that
you think is in reduced functionality mode (meaning you can do next to
nothing with it). Why not put in that PT Biz and format and install it.
Evaluate Vista by using Vista. You don't make mention of XP on that
particular box.

1) Shelby is using a Beta?
2) Shelby has a non-legit copy that went into reduced functionality mode?

1) I think my original post clearly states the copy of Vista I'm using was
received from the PT promo.
2) Why would my copy of Vista from the PT promotional be non-legit?
I'd like to help but I need a post that tells me what's really going on
Shelby.

What is going on is that I have a fresh install of Vista Business on a
system I built that is well within the 30 day evaluation period that
_appears_ to be switching to some sort of reduced functionality mode where I
can still run installed third-party applications yet things like the control
panel, windows welcome center, personalize desktop, etc refuse to open. The
crux of the issue is the fact that once I stop and restart the software
licensing service everything starts working normally and this leads me to
believe that this issue is somehow related to Vista's anti-piracy features.
Vista legit doesn't go into reduced functionality mode lol "without telling
you." And no offense but if you have a Vista that is going to go into

To respond in kind, "LOL RITE". It is clearly _impossible_ that a software
product as complex as Vista could have a _bug_ and Microsoft has _never_,
_ever_ had any bugs or problems with WGA in the past.

Why don't you check out this newsgroup post where someone is having the
_exact_ _same_ _issue_ I'm describing (in fact this was how I figured out
that restarting the SL service as a work-around) with the only material
difference being they've _already_ _activated_ their copy of Vista:

http://groups.google.com/group/micr...e+control+panel&rnum=1&hl=en#f24bc805669d7932
If you think that there are a known percent of Vista legits that go into
reduced functionailty mode, it's a problem I feared would happen given the
erratic WGA performance for a year before Vista RTM'd but hasn't been
reported widely on the web.

I'm not making accusations here and I'm only reporting my experiences. I
find it very difficult to believe that my issue isn't related to Vista's
anti-piracy features since restarting the SL services fixes the issue but
I'll at least admit that there is a possibility that I'm wrong where you seem
to believe that the chances that I'm right is zero.

I'm obviously not the only person experiencing this issue and that is enough
for me regardless of whether or not you believe my issue is related to
Vista's anti-piracy features. Personally, I don't care about anything other
than figuring out the cause of this issue is so that I can utilize the free
copy of Vista I received from the PT promo as opposed to shelling out cash
for an oem version of XP.

Regards,

Shelby Cain
 
Chad Harris said:
Shelby--

Are you in any of these categories? Because if you're presenting a legit
Vista including its product key that has gone into reduced functionality
that you have activated that would be interesting. If I had that case, I'd
call MSFT Activation. Or are you misnaming a situation as reduced
functionality that isn't reduced functionality but is a broken Vista that
can be fixed via Startup Repair accessed from the Vista DVD?

The behavior of reduced functionality mode in Windows Vista
http://support.microsoft.com/kb/925582/en-us

I realize that what I'm experiencing deviates from what you'd expect if
Vista was running in reduced functionality mode and that's why I said
"partial" in my first post. However, I can't help but feel that the fact
that my system starts working normally after I manually stop and start the
licensing service means that this is somehow related to Vista's
anti-tampering/anti-piracy features. This is the third clean install I'm on
and so far this has happened every single time.

I'd be tempted to call Microsoft for support but I really don't want to tie
this copy of Vista to my hardware if there isn't a known solution.

Regards,

Shelby Cain
 
Shelby--

I've complained about bugs that Vista does have as much as anyone. So
you're not springing something on me overnight. I've been using it for a
year and a half--every build.

So far, the issue I'm experiencing is a deal-breaker unless a solution for
my problem becomes
apparent.

You indicate now more clearly that Vista is broken but you are well within
the 30 day period. Those symptoms are quintissential reduced
functionality,but for whatever reason you have them.

You have two choices and a workaround. I've worked with this on somene's
box and I can tell you that all the MSKBs on control panel repair won't
work.

Workaround for control panel not coming up:

You can make a control panel easily by putting the most but not every applet
in a folder. Just make a folder on your desk; type control panel in the
search box>when folder comes up click Classic View and drag or copy everyone
of those shortcuts into your new folder.

Choice One: Format and start over--and activate within 30 days. That gives
you 30 more days to test. If you need to you could renew the 30 days a
couple times.

Or you can try to fix it with Startup Repair using your Power Together
acquired DVD.

I am sorry I misunderstood that you were within the period to activate it at
first. I agree with you it should not have gone into reduced functionality
mode which it appears to have. You should let them know. If this is
happening it confirms some of my fear that SPP would not function well for
everyone; and it would impose reduced functionality on legit Vista either
prior to or after the 30 day period.

One way to directly report this issue is to make a comment on the Vista team
blog, or you could let Darrell Gorter who is directly involved with Vista
setup know

(e-mail address removed)


Choice 2: Try to repair it but I doubt very seriously if it will repair:

You can try the Recovery link that allows you to
use Win RE's Startup Repair or if no joy, System Restore from there which
sometimes works when F8's Safe Mode>System Restore options (all 4 should be
tried) won't.

You can run Startup Repair by putting your Vista DVD in after the
language screen in setup. You can also run System Restore from the same
location.

You run the startup repair tool this way (and system restore from here is
also sometimes effective):

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

Note The computer must be configured to start from a CD or from a DVD. For
information about how to configure the computer to start from a CD or from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your model--go to
pc manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the power
button to turn off the computer. Then, turn the computer back on.

3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically, and you
do not have the option to select it in the System Recovery Options menu.

4. Click Repair your computer.

5. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.

6. In the System Recovery Options menu, click Startup Repair to start the
repair process.

7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore
___________________

You could also:

Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

You will need this reference:

How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/kb/304449/en-us

The command to use for system restore at the safe mode cmd prompt is:

%systemroot%\system32\restore\rstrui.exe

The reason for doing this is one of these choices may work, when the other
doesn't. My experience is that people do not fully try F8 when they think
or have said they have. It is that they can almost always reach Windows
Advanced Options though.


Good luck,

CH





_______________
 
Chad Harris said:
Shelby--

I've complained about bugs that Vista does have as much as anyone. So
you're not springing something on me overnight. I've been using it for a
year and a half--every build.

For what it is worth, the public preview builds of Vista I tested (on
different hardware) worked very well.
You indicate now more clearly that Vista is broken but you are well within
the 30 day period. Those symptoms are quintissential reduced
functionality,but for whatever reason you have them.

You have two choices and a workaround. I've worked with this on somene's
box and I can tell you that all the MSKBs on control panel repair won't
work.

Workaround for control panel not coming up:

You can make a control panel easily by putting the most but not every applet
in a folder. Just make a folder on your desk; type control panel in the
search box>when folder comes up click Classic View and drag or copy everyone
of those shortcuts into your new folder.

I believe (although I can't recall for sure) one of my first attempts was to
make shortcuts to the cpl files in system32. None of the applets would start
up. I'll try and verify that though.
Choice One: Format and start over--and activate within 30 days. That gives
you 30 more days to test. If you need to you could renew the 30 days a
couple times.

I have no problems reformatting and reinstalling to continue testing. I'd
like to get this issue identified as I'm sure I'm not the only one suffering
from it.
I am sorry I misunderstood that you were within the period to activate it at
first. I agree with you it should not have gone into reduced functionality
mode which it appears to have. You should let them know. If this is
happening it confirms some of my fear that SPP would not function well for
everyone; and it would impose reduced functionality on legit Vista either
prior to or after the 30 day period.

Had you asked me two weeks ago if it'd be possible for Vista's anti-piracy
features to malfunction and bite someone that was using a truly legit install
my response would have been "I seriously doubt it as Microsoft would probably
test those features to the nth degree". Now, having experienced this issue
where it _appears_ that Vista is running in some sort of RF mode, I'm not so
sure I'd be confident in saying that. I guess the good thing here is that at
least this issue doesn't appear very widespread.
One way to directly report this issue is to make a comment on the Vista team
blog, or you could let Darrell Gorter who is directly involved with Vista
setup know

(e-mail address removed)

Thanks for the information. I'll post on the blog and contact him privately
and see if he'd be interested in any logs off the machine in question.
Choice 2: Try to repair it but I doubt very seriously if it will repair:

[snip]

I'll probably give that a try eventually but, like you, I'm pretty skeptical
a repair install will help when a clean install hasn't.

Regards,

Shelby Cain
 
Shelby Cain said:
I'll probably give that a try eventually but, like you, I'm pretty skeptical
a repair install will help when a clean install hasn't.

Seems like the 4th clean install may not be acting up. I had planned on
making a restore point after every driver I installed until I was able to
reproduce the issue but it looks like that isn't going to happen.

The interesting thing to note about this install that is different from the
previous three is that the Nvidia 100.65 WHQL drivers were auto-installed via
Windows Update whereas I had to manually install them before with the drivers
obtained from Nvidia's website. I've noticed that the other person
complaining about this issue has the exact same video card I do and I'm
wondering if that is a really just a coincidence.

I'll update this thread if I'm able to reproduce the issue but it seems like
I'm no longer having the issue.

Regards,

Shelby Cain
 
Shelby Cain said:
Seems like the 4th clean install may not be acting up. I had planned on
making a restore point after every driver I installed until I was able to
reproduce the issue but it looks like that isn't going to happen.

The interesting thing to note about this install that is different from the
previous three is that the Nvidia 100.65 WHQL drivers were auto-installed via
Windows Update whereas I had to manually install them before with the drivers
obtained from Nvidia's website. I've noticed that the other person
complaining about this issue has the exact same video card I do and I'm
wondering if that is a really just a coincidence.

I'll update this thread if I'm able to reproduce the issue but it seems like
I'm no longer having the issue.

.... and of course 5 minutes after I made that post it starts doing the same
thing. This is really frustrating.
 
Shelby--

I agree with everything you said. I think Darrell would probably like to
get your logs--he's been consistently helpful on this group and others and
the Beta groups for a long time. In my experience the setup people want to
get to the logs to analyze them if they can provide material that tells what
is going on.

One thing I want to make clear. Although I don't *think a startup repair
(which is different coding in Vista than a repair install in XP will work
with these symptoms, it could and we're only talking about a couple minutes
of time. Doing this has no risk to what you have whatsoever. Here are the
directions for using Vista Win RE's Startup Repair and Safe Mode from that
environmnet.

I put up the steps for doing this (different from an XP repair install
booting from the XP CD) with the Vista DVD on my last post as well as steps
that could work from the F8 aka Windows Advanced Options menu.

You can try the Recovery link that allows you touse Win RE's Startup Repair
or if no joy, System Restore from there whichsometimes works when F8's Safe
Mode>System Restore options (all 4 should be tried):

You can run Startup Repair by putting your Vista DVD in after the
language screen in setup. You can also run System Restore from the same
location.

You run the startup repair tool this way (and system restore from here is
also sometimes effective):

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

Note The computer must be configured to start from a CD or from a DVD. For
information about how to configure the computer to start from a CD or from a
DVD, see the information that came with the computer.
2. Restart the computer. To do this, click Start, click the arrow next to
the Lock button, and then click Restart.

This usually means that you enter bios setup by whatever key or keys
(sometimes there is more than one key that will do it for your model--go to
PC manufacturer site) and configure CD to be first in the boot order.

See for ref:
Access/Enter Motherboard BIOS
http://www.michaelstevenstech.com/bios_manufacturer.htm

Note If you cannot restart the computer by using this method, use the power
button to turn off the computer. Then, turn the computer back on.

3. Set your language preference, and then click Next.

Note In most cases, the startup repair process starts automatically, and you
do not have the option to select it in the System Recovery Options menu.

4. Click Repair your computer.

5. In the System Recovery Options dialog box, click the operating system
that you want to repair, and then click Next.

6. In the System Recovery Options menu, click Startup Repair to start the
repair process.

7. When the repair process is complete, click Finish.

Additional References for Startup Repair With Screenshots:

How to Use Startup Repair:

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore
___________________

You could also:

Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

You will need this reference:

How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/kb/304449/en-us

The command to use for system restore at the safe mode cmd prompt is:

%systemroot%\system32\restore\rstrui.exe

The reason for doing this is one of these choices may work, when the other
doesn't. My experience is that people do not fully try F8 when they think
or have said they have. It is that they can almost always reach Windows
Advanced Options though.


Good luck,

CH







Shelby Cain said:
Chad Harris said:
Shelby--

I've complained about bugs that Vista does have as much as anyone. So
you're not springing something on me overnight. I've been using it for a
year and a half--every build.

For what it is worth, the public preview builds of Vista I tested (on
different hardware) worked very well.
You indicate now more clearly that Vista is broken but you are well
within
the 30 day period. Those symptoms are quintissential reduced
functionality,but for whatever reason you have them.

You have two choices and a workaround. I've worked with this on somene's
box and I can tell you that all the MSKBs on control panel repair won't
work.

Workaround for control panel not coming up:

You can make a control panel easily by putting the most but not every
applet
in a folder. Just make a folder on your desk; type control panel in the
search box>when folder comes up click Classic View and drag or copy
everyone
of those shortcuts into your new folder.

I believe (although I can't recall for sure) one of my first attempts was
to
make shortcuts to the cpl files in system32. None of the applets would
start
up. I'll try and verify that though.
Choice One: Format and start over--and activate within 30 days. That
gives
you 30 more days to test. If you need to you could renew the 30 days a
couple times.

I have no problems reformatting and reinstalling to continue testing. I'd
like to get this issue identified as I'm sure I'm not the only one
suffering
from it.
I am sorry I misunderstood that you were within the period to activate it
at
first. I agree with you it should not have gone into reduced
functionality
mode which it appears to have. You should let them know. If this is
happening it confirms some of my fear that SPP would not function well
for
everyone; and it would impose reduced functionality on legit Vista either
prior to or after the 30 day period.

Had you asked me two weeks ago if it'd be possible for Vista's anti-piracy
features to malfunction and bite someone that was using a truly legit
install
my response would have been "I seriously doubt it as Microsoft would
probably
test those features to the nth degree". Now, having experienced this
issue
where it _appears_ that Vista is running in some sort of RF mode, I'm not
so
sure I'd be confident in saying that. I guess the good thing here is that
at
least this issue doesn't appear very widespread.
One way to directly report this issue is to make a comment on the Vista
team
blog, or you could let Darrell Gorter who is directly involved with
Vista
setup know

(e-mail address removed)

Thanks for the information. I'll post on the blog and contact him
privately
and see if he'd be interested in any logs off the machine in question.
Choice 2: Try to repair it but I doubt very seriously if it will repair:

[snip]

I'll probably give that a try eventually but, like you, I'm pretty
skeptical
a repair install will help when a clean install hasn't.

Regards,

Shelby Cain
 
Chad Harris said:
Shelby--

I agree with everything you said. I think Darrell would probably like to
get your logs--he's been consistently helpful on this group and others and
the Beta groups for a long time. In my experience the setup people want to
get to the logs to analyze them if they can provide material that tells what
is going on.

One thing I want to make clear. Although I don't *think a startup repair
(which is different coding in Vista than a repair install in XP will work
with these symptoms, it could and we're only talking about a couple minutes
of time. Doing this has no risk to what you have whatsoever. Here are the
directions for using Vista Win RE's Startup Repair and Safe Mode from that
environmnet.

I'll give it a shot just for completeness.

However, I've finally figured out what triggers the problem... booting
without the Vista install media present in my dvd drive....

I've just rebooted 10 times in a row with the install media in my dvd drive
and each time Vista is fully functional (control panel, windows welcome
center, etc) once I log into my desktop. As soon as I remove the media from
my dvd drive and reboot, Vista returns to the behavior I originally reported.
O_o

I don't even know what to think at this point.

Regards,

Shelby Cain
 
Shelby--

Take a look at this thread started by Richard Urban on this group recently.
I think there may be a connection between what you're experiencing or if
not, at least the need to supply the DVD to boot with full functionality is
a common denominator. I understand the scenario Richard paints is one where
Vista will not boot:

Vista will not boot - work around
Saturday, March 03, 2007 2:51 PM


I have installed the various versions of Vista on 56 various computers. On
eight of those computers I have run into, and solved, this nasty boot
problem. I have also assisted with this problem for a rather large handful
of people who post here with a similar condition.

The problem concerns computers with the following configuration/condition:

1. A computer with multiple hard drives (any mix of S-ATA or PATA it
turns out)

2. Any of the 2nd, or higher, drives has been setup as having a logical
partition/partitions

3. The user installs Vista by booting from the DVD

When a drive is setup with a logical partition, 8 meg of unallocated space
is reserved at the beginning of the drive.

The Vista installer, it appears, will start installing boot code to the
unallocated space on a 2nd, 3rd or 4th drive. I have used a hex editor and
have found this code there. This 8 meg of unallocated space is quickly
filled and the installer places the remainder of the code on the disk chosen
by the user for the Vista install.

The Vista install completes and the user removes the DVD. Upon startup, the
user finds that Vista will not boot. Vista is looking for the boot code on
the drive where the user had chosen to install Vista (system partition). It
is not there. Part of it resides on another drive where it is not
recognized.

If the user puts the DVD into the drive tray, Vista boots fine. Startup
takes the code from the DVD.

This should not occur, but it is too late to change the code on the Vista
DVD's at this point. The work around is to physically disconnect any drive
that you do not want the Vista installer to touch. In this way, all of the
code is written to the desired drive/partition.

Upon arriving at the Windows desktop, go to system management | Disk
Management and change the drive letters for your CD drive, DVD drive, USB
drives, card readers etc. to the end of the alphabet. This gets them out of
the way prior to you shutting down the computer and reconnecting your other
drives.

Now, shut down your computer and reconnect your drives. Upon booting to the
desktop, you will see that the new drives are recognized and initialized.
You will also see that the drive letters are in sequence, and not broken up
by the various other drives (you previously moved them). You may be asked to
reboot so the changes can be made permanent. Do so if directed.

The next time you boot to the desktop you can rearrange those re-lettered
drives if you so desire.

Now, I am not certain how pervasive this problem is but I have seen it on
old/new motherboards from 3 major M/B manufacturers. It is not, of course,
going to affect those who purchase a new computer with Vista on it. It
"will" affect those who upgrade or build their own computers, as these are
the users who are more likely to have multiple drives installed in their
machines.


--


Regards,

Richard Urban MVP
Microsoft Windows Shell/User
________________________________

CH
 
Hello Shelby,
Please sent me the application logs from the machine.
\Remove the online from my email addres.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>Thread-Topic: Vista entering reduced functionality mode without warning
|>thread-index: Acdd3obStNAy22WTTNWqm8BDCXlFNg==
|>X-WBNR-Posting-Host: 70.250.177.197
|>From: =?Utf-8?B?U2hlbGJ5IENhaW4=?= <[email protected]>
|>References: <[email protected]>
<[email protected]>
<[email protected]>
<#[email protected]>
<[email protected]>
<#[email protected]>
|>Subject: Re: Vista entering reduced functionality mode without warning
|>Date: Sat, 3 Mar 2007 13:54:32 -0800
|>Lines: 38
|>Message-ID: <[email protected]>
|>MIME-Version: 1.0
|>Content-Type: text/plain;
|> charset="Utf-8"
|>Content-Transfer-Encoding: 7bit
|>X-Newsreader: Microsoft CDO for Windows 2000
|>Content-Class: urn:content-classes:message
|>Importance: normal
|>Priority: normal
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
|>Newsgroups: microsoft.public.windows.vista.installation_setup
|>Path: TK2MSFTNGHUB02.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup:11219
|>NNTP-Posting-Host: TK2MSFTSBFM01 10.40.244.148
|>X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|>
|>
|>
|>"Chad Harris" wrote:
|>
|>> Shelby--
|>>
|>> I agree with everything you said. I think Darrell would probably like
to
|>> get your logs--he's been consistently helpful on this group and others
and
|>> the Beta groups for a long time. In my experience the setup people
want to
|>> get to the logs to analyze them if they can provide material that tells
what
|>> is going on.
|>>
|>> One thing I want to make clear. Although I don't *think a startup
repair
|>> (which is different coding in Vista than a repair install in XP will
work
|>> with these symptoms, it could and we're only talking about a couple
minutes
|>> of time. Doing this has no risk to what you have whatsoever. Here are
the
|>> directions for using Vista Win RE's Startup Repair and Safe Mode from
that
|>> environmnet.
|>>
|>
|>I'll give it a shot just for completeness.
|>
|>However, I've finally figured out what triggers the problem... booting
|>without the Vista install media present in my dvd drive....
|>
|>I've just rebooted 10 times in a row with the install media in my dvd
drive
|>and each time Vista is fully functional (control panel, windows welcome
|>center, etc) once I log into my desktop. As soon as I remove the media
from
|>my dvd drive and reboot, Vista returns to the behavior I originally
reported.
|> O_o
|>
|>I don't even know what to think at this point.
|>
|>Regards,
|>
|>Shelby Cain
|>
|>
|>
 
Back
Top