Vista - Suddenly lost [ctrl] and [shift] key functionality in Explorer

Yesterday I suddenly lost the ability to select more than one file in Windows
Explorer and "This computer" using the [ctrl]- and [shift]-key. Also the
option "Select all" in the Edit menu is disabled.

If I use an "open file dialog" (from Word og elsewhere) I have no problem
selecting more than one file.

If I log into another account I have no problem.

I have tried resetting all folders via "folder option" but that doesn't help.

I really don't want to have to transfer all my settings to a new account if
there is some other way to get the [ctrl] and [shift] keys to work again
under this account :-)

Can anyone help me?

I've seen this posted as well. Haven't experienced it -- but I was able to
induce this behavior in a particular folder by regediting the saved view --
but even when I tried 'Apply to Folders', it didn't seem to affect others.

It does seem that once a folder has gotten into this mode, it is saved with
its view settings, so see if the following helps:

With all explorer windows closed, export & then delete the
following registry key (this will erase saved folder views):

"HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags"

Log off & log back on. See if that fixes it.


--
Good Luck,

Keith
Microsoft MVP [Windows XP Shell/User]

"Soeren Soeby" <Soeren Soeby@discussions.microsoft.com> wrote in message
news:2638E706-8467-47B3-A647-05AFBEFC716A@microsoft.com...
> Yesterday I suddenly lost the ability to select more than one file in
> Windows
> Explorer and "This computer" using the [ctrl]- and [shift]-key. Also the
> option "Select all" in the Edit menu is disabled.
>
> If I use an "open file dialog" (from Word og elsewhere) I have no problem
> selecting more than one file.
>
> If I log into another account I have no problem.
>
> I have tried resetting all folders via "folder option" but that doesn't
> help.
>
> I really don't want to have to transfer all my settings to a new account
> if
> there is some other way to get the [ctrl] and [shift] keys to work again
> under this account :-)
>
> Can anyone help me?

Hi Keith

Thank you for your answer and suggestion - and time!

I am sorry that I haven't writen this sooner, but I have already delt with
the problem using a "restore point" because I had to use my computer
extensively today.

If the problem reappears I will test your suggestion and report back to this
community.

Kind regards
- Soeren

Thanks for the feedback. Keep us posted.


--
Good Luck,

Keith
Microsoft MVP [Windows XP Shell/User]

"Soeren Soeby" <SoerenSoeby@discussions.microsoft.com> wrote in message
news:8B188A54-5903-4378-9D4A-0EC13E541FBC@microsoft.com...
> Hi Keith
>
> Thank you for your answer and suggestion - and time!
>
> I am sorry that I haven't writen this sooner, but I have already delt with
> the problem using a "restore point" because I had to use my computer
> extensively today.
>
> If the problem reappears I will test your suggestion and report back to
> this
> community.
>
> Kind regards
> - Soeren

On Sat, 17 Feb 2007 16:09:58 -0600, "Keith Miller MVP"

>Thanks for the feedback. Keep us posted.

I've just replied to a similar thread in an XP newsgroup, where this
was attributed to SP2 (the topic may be "sp2").

I wonder if there isn't a 3rd-party app that is doing some shell
integration that breaks in SP2 and later code bases?

Perhaps we should ask what apps, mouse and graphics enhancements etc.
folks with these problems are using, to see if there's anythin in
common? Or maybe there's an Accessibility feature that got turned on
by mistake, something like StickyKeys?



>--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
>--------------- ---- --- -- - - - -

"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote in
message news:v69gt2974blthf6329a6b13ho6me0eubpa@4ax.com...
> On Sat, 17 Feb 2007 16:09:58 -0600, "Keith Miller MVP"
>
>>Thanks for the feedback. Keep us posted.
>
> I've just replied to a similar thread in an XP newsgroup, where this
> was attributed to SP2 (the topic may be "sp2").
>
> I wonder if there isn't a 3rd-party app that is doing some shell
> integration that breaks in SP2 and later code bases?
>
> Perhaps we should ask what apps, mouse and graphics enhancements etc.
> folks with these problems are using, to see if there's anythin in
> common? Or maybe there's an Accessibility feature that got turned on
> by mistake, something like StickyKeys?
>

It would be great to gather that info, but it's hard enough to get basic
responses sometimes

I don't think it's StickyKeys. It's the result of a flag from this group:

http://msdn2.microsoft.com/en-us/library/ms649291.aspx

The bothersome value is "FWF_SINGLESEL = 0x00000040"

How it initially gets set is currently a mystery. But the problem can be
compounded because once set, it is saved with the folder view:

"HKCU\Software\Classes\Local
Settings\Software\Microsoft\Windows\Shell\Bags\<Bag#>\Shell\{TemplateUUID}

in the value named 'FFlags'.

If the user happened to use 'Apply to folders' while this was in effect, it
is saved and applied to all folders that use that template (Sort of -- but
I'm trying to keep this brief).

I'm going to write a script to correct the settings (that I've currently
found) without wiping out all saved views & custom defaults -- but still
would like to know the underlying cause.


--
Good Luck,

Keith
Microsoft MVP [Windows XP Shell/User]

On Sun, 18 Feb 2007 12:07:29 -0600, "Keith Miller MVP"
>"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org>
>> On Sat, 17 Feb 2007 16:09:58 -0600, "Keith Miller MVP"

>> I've just replied to a similar thread in an XP newsgroup, where this
>> was attributed to SP2 (the topic may be "sp2").

>> I wonder if there isn't a 3rd-party app that is doing some shell
>> integration that breaks in SP2 and later code bases?

>> Perhaps we should ask what apps, mouse and graphics enhancements etc.
>> folks with these problems are using, to see if there's anythin in
>> common? Or maybe there's an Accessibility feature that got turned on
>> by mistake, something like StickyKeys?

>It would be great to gather that info, but it's hard enough to get basic
>responses sometimes

IKWYM... it's actually quite hard work pinning down bugs, even as far
as finding a minimum test that will always repro, and then describing
the whole thing formally enough for others to test.

>I don't think it's StickyKeys. It's the result of a flag from this group:

>http://msdn2.microsoft.com/en-us/library/ms649291.aspx

Lovely reference!! I'd like to apply these...

FWF_NOICONS
The view should not display icons.

FWF_NOWEBVIEW
The view should not be shown as a Web view.

FWF_CHECKSELECT
Turns on the check mode for the view.

FWF_NOFILTERS
Windows Vista: Do not display filters in the view.

FWF_AUTOCHECKSELECT
Windows Vista: Items can be selected using checkboxes.

....for a "Safe List" mode.

>The bothersome value is "FWF_SINGLESEL = 0x00000040"

OK, that may make sense...

FWF_SINGLESEL
Do not allow more than a single item to be selected. This is used in
the common dialog boxes.

Common dialogs are expected to be used to select a signgle item to
have a pre-determined action applied to it. They're flexible enough
to allow rt-click actions, New, etc. but I can see why one might not
want them used as drop targets etc.

>How it initially gets set is currently a mystery.

*that's* the bug. It could happen if a common dialog sets the flag
when "in" that location and fails to clear it if a bad exit happens
before the dialog is closed or aborted.

>But the problem can be compounded because once set, it is saved
>with the folder view:

>"HKCU\Software\Classes\Local
>Settings\Software\Microsoft\Windows\Shell\Bags\<Bag#>\Shell\{TemplateUUID}

>in the value named 'FFlags'.

>If the user happened to use 'Apply to folders' while this was in effect, it
>is saved and applied to all folders that use that template (Sort of -- but
>I'm trying to keep this brief).

OK, I can see why that would suck...

>I'm going to write a script to correct the settings (that I've currently
>found) without wiping out all saved views & custom defaults -- but still
>would like to know the underlying cause.

Me2. This is slippery stuff; looks like you know your way around it,
though. Do you have any other pertinent URLs on these things?



>--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
>--------------- ---- --- -- - - - -

"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote in
message newsd7kt29fjhi4q1fvg5338drcpqgfnbnho9@4ax.com...
> On Sun, 18 Feb 2007 12:07:29 -0600, "Keith Miller MVP"
>>"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org>
>>> On Sat, 17 Feb 2007 16:09:58 -0600, "Keith Miller MVP"
>
>>> I've just replied to a similar thread in an XP newsgroup, where this
>>> was attributed to SP2 (the topic may be "sp2").
>
>>> I wonder if there isn't a 3rd-party app that is doing some shell
>>> integration that breaks in SP2 and later code bases?
>
>>> Perhaps we should ask what apps, mouse and graphics enhancements etc.
>>> folks with these problems are using, to see if there's anythin in
>>> common? Or maybe there's an Accessibility feature that got turned on
>>> by mistake, something like StickyKeys?
>
>>It would be great to gather that info, but it's hard enough to get basic
>>responses sometimes
>
> IKWYM... it's actually quite hard work pinning down bugs, even as far
> as finding a minimum test that will always repro, and then describing
> the whole thing formally enough for others to test.
>
>>I don't think it's StickyKeys. It's the result of a flag from this group:
>
>>http://msdn2.microsoft.com/en-us/library/ms649291.aspx
>
> Lovely reference!! I'd like to apply these...
>
> FWF_NOICONS
> The view should not display icons.
>
> FWF_NOWEBVIEW
> The view should not be shown as a Web view.
>
> FWF_CHECKSELECT
> Turns on the check mode for the view.
>
> FWF_NOFILTERS
> Windows Vista: Do not display filters in the view.
>
> FWF_AUTOCHECKSELECT
> Windows Vista: Items can be selected using checkboxes.
>
> ...for a "Safe List" mode.

Actually, FWF_NOICONS makes a folder look empty, even when it's not --
suppresses text as well as icons.

>
>>The bothersome value is "FWF_SINGLESEL = 0x00000040"
>
> OK, that may make sense...
>
> FWF_SINGLESEL
> Do not allow more than a single item to be selected. This is used in
> the common dialog boxes.
>
> Common dialogs are expected to be used to select a signgle item to
> have a pre-determined action applied to it. They're flexible enough
> to allow rt-click actions, New, etc. but I can see why one might not
> want them used as drop targets etc.
>
>>How it initially gets set is currently a mystery.
>
> *that's* the bug. It could happen if a common dialog sets the flag
> when "in" that location and fails to clear it if a bad exit happens
> before the dialog is closed or aborted.
>

The common dialog view for a folder is seperate from the folder view. When
I first browsed the registry, under HKCU\...\<Bag#>\ComDlg, all the FFlags'
were 0x00000001. Running RegMon while using the dialog under notepad shows
that the value is changed to 0x40200041 and then back to 0x00000001 the
moment an item is open/saved. But the behavior is in effect the entire time
the dialog is open. I tried creating a new folder via the 'Open' dialog --
then right-clicking & 'exploring' the new folder, but it still behaved fine.


>>But the problem can be compounded because once set, it is saved
>>with the folder view:
>
>>"HKCU\Software\Classes\Local
>>Settings\Software\Microsoft\Windows\Shell\Bags\<Bag#>\Shell\{TemplateUUID}
>
>>in the value named 'FFlags'.
>
>>If the user happened to use 'Apply to folders' while this was in effect,
>>it
>>is saved and applied to all folders that use that template (Sort of -- but
>>I'm trying to keep this brief).
>
> OK, I can see why that would suck...
>
>>I'm going to write a script to correct the settings (that I've currently
>>found) without wiping out all saved views & custom defaults -- but still
>>would like to know the underlying cause.
>
> Me2. This is slippery stuff; looks like you know your way around it,
> though. Do you have any other pertinent URLs on these things?
>

Nope, sorry.


--
Good Luck,

Keith
Microsoft MVP [Windows XP Shell/User]

On Mon, 19 Feb 2007 22:14:06 -0600, "Keith Miller MVP"
>"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote

>Actually, FWF_NOICONS makes a folder look empty, even when it's not --
>suppresses text as well as icons.

Oops...

>>>The bothersome value is "FWF_SINGLESEL = 0x00000040"
>>>How it initially gets set is currently a mystery.
>>
>> *that's* the bug. It could happen if a common dialog sets the flag
>> when "in" that location and fails to clear it if a bad exit happens
>> before the dialog is closed or aborted.

>The common dialog view for a folder is seperate from the folder view. When
>I first browsed the registry, under HKCU\...\<Bag#>\ComDlg, all the FFlags'
>were 0x00000001. Running RegMon while using the dialog under notepad shows
>that the value is changed to 0x40200041 and then back to 0x00000001 the
>moment an item is open/saved. But the behavior is in effect the entire time
>the dialog is open. I tried creating a new folder via the 'Open' dialog --
>then right-clicking & 'exploring' the new folder, but it still behaved fine.

OK. Was thinking it may have been left as 40200041 if there was a
bad-exit before that dialog was closed.



>--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
>--------------- ---- --- -- - - - -

I lost the ability to select more than 1 file again the other day so I tried
deleting the registry key "bags" and... I WORKED!

Thank you very much!