Vista Tutorial - Unable to backup stored logon credentials - anyone else?

Vista x64 RTM

Control Panel, User Accounts, Manage your network passwords, Backup

I'm prompted for a lcoation (C:\X.crd) and I'm then prompted to press
Ctrt+Alt+Delete. I then enter a password.

I've then shown a screen "A device attached to your system is not
functioning".

I've tried backing up to different locations, but I always get the
same message.

Can anyone else get this to work?


Many thanks,



Jim

Jim--

Mine works and has all builds. It sounds as if simply a .dll or file there
is corrupted. Try running System File checker by typing into an elevated
cmd prompt sfc/ scannow. Right click cmd and click "run as administrator."
See if that fixes it.

If it's just backing up the password, I don't know why default behavior
won't let you do this. I haven't tried to backup the password.

You can always email it to yourself including web based email and then you
have a backup anytime anywhere.

You can also try to see if you can recover/backup any passwords with this
utility but I think that the above solution will work for you:

www.nirsoft.net PSPV at www.nirsoft.net/utils/pspv.html and you can also
check their password utilities here:
http://www.nirsoft.net/password_recovery_tools.html


This may be of some help but I still think it's a file corruption problem.

UAC blog on the Windows login prompt
http://blogs.msdn.com/uac/archive/20...ame-field.aspx

and I noticed this Jim from Daniel Oliver on the Windows Shell Team who I
imagine works closely with UAC in integrating security for Windows login at
the above link:

"Is it possible to get the old default behavior back?

Yes, it is. The behavior is controlled by a Group Policy setting and can be
configured using gpedit.msc. Once in the MMC snap-in, use the tree control
to navigate to...

Local Computer Policy -> Computer Configuration -> Administrative
Templates -> Windows Components -> Credential User Interface -> Enumerate
administrator accounts on elevation

"Enable this Group Policy setting.

Why did the UAC team make this change?

During enumeration of local machine administrators, the system must contact
a domain controller (DC). While this enumeration occurred, an indeterminate
progress bar appeared within the user list region. We received a large
amount of feedback regarding the long period of time this progress bar took
to disappear. We analyzed the problem in detail and found users experiencing
unusually slow performance when the DC was unavailable or slow to respond.
In order to place the dialog box in front of users as fast as possible, we
changed the default behavior. Speed.

How do I change the domain field?

By default, the Password Provider will pre-append the domain (or machine
name in the workgroup case) to serialized credentials. The uneditable string
below the password field indicates the domain (or machine name) that will be
used. To specify a different domain, it must be entered in the user name
field. The correct format is domain\username or username@domain. The domain
field will update automatically. This is the same convention used during
logon.

How does this Group Policy setting function on workgroup machines?

Enumerate administrator accounts on elevation has a slightly different
meaning on workgroup machines. By default (that is, the setting has been
neither enabled nor disabled), the Password Provider will list all local
administrators on the machine. When enabled or disabled, this policy behaves
exactly the same as in the domain-joined scenario.

How does this Group Policy setting affect other credential providers?

The Microsoft Smart Card Provider is not affected at all by this change. We
recommended credential providers written by ISVs respect the settings in
Group Policy."

-- Daniel Oliver

Windows Shell Team

Published Thursday, October 12, 2006 7:24 AM by User Account Control Team


Also check on other interesting security references:

http://blogs.msdn.com/windowsvistasecurity/

http://blogs.technet.com/steriley/

Why administrative passwords will never be like nuclear missile launchers
http://blogs.technet.com/steriley/ar...launchers.aspx

CH

"Jim" <jim@nospam.com> wrote in message
news:7hlao251o9bdaausauvm5d4j89llji16rv@4ax.com...
> Vista x64 RTM
>
> Control Panel, User Accounts, Manage your network passwords, Backup
>
> I'm prompted for a lcoation (C:\X.crd) and I'm then prompted to press
> Ctrt+Alt+Delete. I then enter a password.
>
> I've then shown a screen "A device attached to your system is not
> functioning".
>
> I've tried backing up to different locations, but I always get the
> same message.
>
> Can anyone else get this to work?
>
>
> Many thanks,
>
>
>
> Jim

Hi Chad,

Many thanks for taking the time.

Unfortunately, no joy. SFC found no integrity violations.

V64 is installed on an NTFS partition (Intel Matrix RAID 1). I have
UAC disabled (doesn't everyone?). What I'm confused about is what
"device" is it complaining about? I'd look in the event viewer, except
it's now a nightmare in Vista there's so many logs and sections!

All I'm trying to do is create abackup of all the stored passwords. I
have around 15 RDP connections to other systems and I've stored all
the credentials into the key manager. I don't really want to lose
these when I reinstall (which I'm expecting to do frequently over the
next month or so as part of our evaluation).

If I could identify what device it was complaining about then it might
be a start. I've tried backing up to the C: drive and my USB flash
drive (J. Any ideas how I would diagnose this? I can't imagine why
it would be looking for a device, other than the destination. The
message appears instantly, as soon as I have entered my password and
clicked to proceed.

My machine is standalone, not on a domain.

Cheers,



Jim




..On Sun, 17 Dec 2006 12:43:06 -0500, "Chad Harris"
<msftneedstogetoutvistainfo.net> wrote:

>Jim--
>
>Mine works and has all builds. It sounds as if simply a .dll or file there
>is corrupted. Try running System File checker by typing into an elevated
>cmd prompt sfc/ scannow. Right click cmd and click "run as administrator."
>See if that fixes it.
>
>If it's just backing up the password, I don't know why default behavior
>won't let you do this. I haven't tried to backup the password.
>
>You can always email it to yourself including web based email and then you
>have a backup anytime anywhere.
>
>You can also try to see if you can recover/backup any passwords with this
>utility but I think that the above solution will work for you:
>
>www.nirsoft.net PSPV at www.nirsoft.net/utils/pspv.html and you can also
>check their password utilities here:
>http://www.nirsoft.net/password_recovery_tools.html
>
>
>This may be of some help but I still think it's a file corruption problem.
>
>UAC blog on the Windows login prompt
>http://blogs.msdn.com/uac/archive/20...ame-field.aspx
>
>and I noticed this Jim from Daniel Oliver on the Windows Shell Team who I
>imagine works closely with UAC in integrating security for Windows login at
>the above link:
>
>"Is it possible to get the old default behavior back?
>
>Yes, it is. The behavior is controlled by a Group Policy setting and can be
>configured using gpedit.msc. Once in the MMC snap-in, use the tree control
>to navigate to...
>
>Local Computer Policy -> Computer Configuration -> Administrative
>Templates -> Windows Components -> Credential User Interface -> Enumerate
>administrator accounts on elevation
>
>"Enable this Group Policy setting.
>
>Why did the UAC team make this change?
>
>During enumeration of local machine administrators, the system must contact
>a domain controller (DC). While this enumeration occurred, an indeterminate
>progress bar appeared within the user list region. We received a large
>amount of feedback regarding the long period of time this progress bar took
>to disappear. We analyzed the problem in detail and found users experiencing
>unusually slow performance when the DC was unavailable or slow to respond.
>In order to place the dialog box in front of users as fast as possible, we
>changed the default behavior. Speed.
>
>How do I change the domain field?
>
>By default, the Password Provider will pre-append the domain (or machine
>name in the workgroup case) to serialized credentials. The uneditable string
>below the password field indicates the domain (or machine name) that will be
>used. To specify a different domain, it must be entered in the user name
>field. The correct format is domain\username or username@domain. The domain
>field will update automatically. This is the same convention used during
>logon.
>
>How does this Group Policy setting function on workgroup machines?
>
>Enumerate administrator accounts on elevation has a slightly different
>meaning on workgroup machines. By default (that is, the setting has been
>neither enabled nor disabled), the Password Provider will list all local
>administrators on the machine. When enabled or disabled, this policy behaves
>exactly the same as in the domain-joined scenario.
>
>How does this Group Policy setting affect other credential providers?
>
>The Microsoft Smart Card Provider is not affected at all by this change. We
>recommended credential providers written by ISVs respect the settings in
>Group Policy."
>
>-- Daniel Oliver
>
>Windows Shell Team
>
>Published Thursday, October 12, 2006 7:24 AM by User Account Control Team
>
>
>Also check on other interesting security references:
>
>http://blogs.msdn.com/windowsvistasecurity/
>
>http://blogs.technet.com/steriley/
>
>Why administrative passwords will never be like nuclear missile launchers
>http://blogs.technet.com/steriley/ar...launchers.aspx
>
>CH
>
>"Jim" <jim@nospam.com> wrote in message
>news:7hlao251o9bdaausauvm5d4j89llji16rv@4ax.com...
>> Vista x64 RTM
>>
>> Control Panel, User Accounts, Manage your network passwords, Backup
>>
>> I'm prompted for a lcoation (C:\X.crd) and I'm then prompted to press
>> Ctrt+Alt+Delete. I then enter a password.
>>
>> I've then shown a screen "A device attached to your system is not
>> functioning".
>>
>> I've tried backing up to different locations, but I always get the
>> same message.
>>
>> Can anyone else get this to work?
>>
>>
>> Many thanks,
>>
>>
>>
>> Jim

I don't know how you pick off the offending device if it's the cause, unless
you have added some recent device or devices, and then wanted to try
uninstalling them empirically using the history of when you installed them.

It would be nice if there were some pinpoint diagnostic method, but I don't
know what that is. There are lots of third party gizmos both software and
hdw I've seen that purport to do that, but I don't believe them.

That reminds me of some of the most ridiculous BSOD stops on the planet that
MSFT has come up with that say "we have shut down your computer because of a
kernel stack driver or words to that effect offending etc. device driver."

That would raise the question which one? If you put driver query at the
command prompt you're going to get a list of about 200-250 kernel stack
drivers in XP or Vista or more, and 35 or so non-lernel stack drivers in
XP--I don't know what happened to non-kernel stack drivers in Vista. (I
know Jim Allchin blogged it loads with 19,500 but that's not what you see
using the command drivequery sot it obviously lists drivers in use not
drivers for potential use by a lot of different hardware and software
equations from users).


Event Viewer in Vista is confusing at first and more complicated but it
still merits a look in applications and system because you may turn up a
nugget that can help you.

You might want to run the little app PSPV I linked from Nirsoft, because
what it will do is spit out most of your passwords into a notepad--maybe all
of them. Then you can simply copy the notepad and email it to yourself
which is a nice quick poor man's backup. I use email to put a lot of
articles or tips that I want to save on someone else's server.

And unless you have very sensitive information, I don't think that
compromises you. Or as a work around althought primitive, you can burn
them to DVD or if you still had smaller media that has all but disappeared
from pcs, a floppy disc like people did back in the day.

I admit not having mastered all the nuances of Vista's more sophisticated
EV, but it's because I haven't felt the compelling need to--I'll get around
to studying it.

If you've done this before, but can't now, you could always try some system
restore points if you knew when it stopped backing up passwords, but I'm
guessing this is the first time you tried it.

You could always try Startup Repair and see if that makes a difference:

You run the startup repair tool this way:

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

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreins...rtup/index.htm

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

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img...SysRecOpt2.bmp


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.

Good luck,

CH


"Jim" <jim@nospam.com> wrote in message
news:jp2bo2pe6r2libhupjfjog5p8mqf2kbbdj@4ax.com...
> Hi Chad,
>
> Many thanks for taking the time.
>
> Unfortunately, no joy. SFC found no integrity violations.
>
> V64 is installed on an NTFS partition (Intel Matrix RAID 1). I have
> UAC disabled (doesn't everyone?). What I'm confused about is what
> "device" is it complaining about? I'd look in the event viewer, except
> it's now a nightmare in Vista there's so many logs and sections!
>
> All I'm trying to do is create abackup of all the stored passwords. I
> have around 15 RDP connections to other systems and I've stored all
> the credentials into the key manager. I don't really want to lose
> these when I reinstall (which I'm expecting to do frequently over the
> next month or so as part of our evaluation).
>
> If I could identify what device it was complaining about then it might
> be a start. I've tried backing up to the C: drive and my USB flash
> drive (J. Any ideas how I would diagnose this? I can't imagine why
> it would be looking for a device, other than the destination. The
> message appears instantly, as soon as I have entered my password and
> clicked to proceed.
>
> My machine is standalone, not on a domain.
>
> Cheers,
>
>
>
> Jim
>
>
>
>
> .On Sun, 17 Dec 2006 12:43:06 -0500, "Chad Harris"
> <msftneedstogetoutvistainfo.net> wrote:
>
>>Jim--
>>
>>Mine works and has all builds. It sounds as if simply a .dll or file
>>there
>>is corrupted. Try running System File checker by typing into an elevated
>>cmd prompt sfc/ scannow. Right click cmd and click "run as
>>administrator."
>>See if that fixes it.
>>
>>If it's just backing up the password, I don't know why default behavior
>>won't let you do this. I haven't tried to backup the password.
>>
>>You can always email it to yourself including web based email and then you
>>have a backup anytime anywhere.
>>
>>You can also try to see if you can recover/backup any passwords with this
>>utility but I think that the above solution will work for you:
>>
>>www.nirsoft.net PSPV at www.nirsoft.net/utils/pspv.html and you can also
>>check their password utilities here:
>>http://www.nirsoft.net/password_recovery_tools.html
>>
>>
>>This may be of some help but I still think it's a file corruption problem.
>>
>>UAC blog on the Windows login prompt
>>http://blogs.msdn.com/uac/archive/20...ame-field.aspx
>>
>>and I noticed this Jim from Daniel Oliver on the Windows Shell Team who I
>>imagine works closely with UAC in integrating security for Windows login
>>at
>>the above link:
>>
>>"Is it possible to get the old default behavior back?
>>
>>Yes, it is. The behavior is controlled by a Group Policy setting and can
>>be
>>configured using gpedit.msc. Once in the MMC snap-in, use the tree control
>>to navigate to...
>>
>>Local Computer Policy -> Computer Configuration -> Administrative
>>Templates -> Windows Components -> Credential User Interface -> Enumerate
>>administrator accounts on elevation
>>
>>"Enable this Group Policy setting.
>>
>>Why did the UAC team make this change?
>>
>>During enumeration of local machine administrators, the system must
>>contact
>>a domain controller (DC). While this enumeration occurred, an
>>indeterminate
>>progress bar appeared within the user list region. We received a large
>>amount of feedback regarding the long period of time this progress bar
>>took
>>to disappear. We analyzed the problem in detail and found users
>>experiencing
>>unusually slow performance when the DC was unavailable or slow to respond.
>>In order to place the dialog box in front of users as fast as possible, we
>>changed the default behavior. Speed.
>>
>>How do I change the domain field?
>>
>>By default, the Password Provider will pre-append the domain (or machine
>>name in the workgroup case) to serialized credentials. The uneditable
>>string
>>below the password field indicates the domain (or machine name) that will
>>be
>>used. To specify a different domain, it must be entered in the user name
>>field. The correct format is domain\username or username@domain. The
>>domain
>>field will update automatically. This is the same convention used during
>>logon.
>>
>>How does this Group Policy setting function on workgroup machines?
>>
>>Enumerate administrator accounts on elevation has a slightly different
>>meaning on workgroup machines. By default (that is, the setting has been
>>neither enabled nor disabled), the Password Provider will list all local
>>administrators on the machine. When enabled or disabled, this policy
>>behaves
>>exactly the same as in the domain-joined scenario.
>>
>>How does this Group Policy setting affect other credential providers?
>>
>>The Microsoft Smart Card Provider is not affected at all by this change.
>>We
>>recommended credential providers written by ISVs respect the settings in
>>Group Policy."
>>
>>-- Daniel Oliver
>>
>>Windows Shell Team
>>
>>Published Thursday, October 12, 2006 7:24 AM by User Account Control Team
>>
>>
>>Also check on other interesting security references:
>>
>>http://blogs.msdn.com/windowsvistasecurity/
>>
>>http://blogs.technet.com/steriley/
>>
>>Why administrative passwords will never be like nuclear missile launchers
>>http://blogs.technet.com/steriley/ar...launchers.aspx
>>
>>CH
>>
>>"Jim" <jim@nospam.com> wrote in message
>>news:7hlao251o9bdaausauvm5d4j89llji16rv@4ax.com...
>>> Vista x64 RTM
>>>
>>> Control Panel, User Accounts, Manage your network passwords, Backup
>>>
>>> I'm prompted for a lcoation (C:\X.crd) and I'm then prompted to press
>>> Ctrt+Alt+Delete. I then enter a password.
>>>
>>> I've then shown a screen "A device attached to your system is not
>>> functioning".
>>>
>>> I've tried backing up to different locations, but I always get the
>>> same message.
>>>
>>> Can anyone else get this to work?
>>>
>>>
>>> Many thanks,
>>>
>>>
>>>
>>> Jim

---------
I've got the same problem (Vista Enterprise x86). In my case, it's been working for over a year (backing up the credentials to a second NTFS/SAS drive). All of a sudden, it quit working. And, just like you, the actual error message is bogus.

Looks like it's time to get Microsoft CSS to work the issue. Have you by chance opened a case yet?

Regards,

Stuart.

No I've not opened a case.

I've actually reinstalled my laptop since then, and I did get it to work. But I've just tried again today and got the same error...no new devices, no new software.

Vista x64 Business SP1.


Jim