Problem with IShellBrowser hosting the Desktop with recent Windows Update
Jonathan Potter
A recent windows update (KB921398) has caused some problems with our
software, Directory Opus.
Our app implements IShellBrowser. With KB921398 applied, double-clicks on
folders and other items like zip files do not work in the Desktop folder
when it is being hosted in our app. Additionally, context menus on these
items also do not work (no menu appears at all when the right button is
clicked).
Uninstalling KB921398 through appwiz.cpl fixes the problem immediately, so
it is obviously caused by this patch.
Regards,
Jonathan Potter
GP Software
Jeffrey Tan[MSFT]
I have performed some search in both public resource and internal database,
can not find any existing issue regarding KB921398 and IShellBrowser, so it
seems that this issue is not reported before.
Is it possible for you to create a little sample project regarding this
issue? If so, please feel free to provide it to me. Once I can reproduce
this issue, I will help you to contact our product team for this issue.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Jim Barry
> I have performed some search in both public resource and internal
> database, can not find any existing issue regarding KB921398 and
> IShellBrowser, so it seems that this issue is not reported before.
Presumably this is the same issue as reported in the 17 August post in this newsgroup, subject line "KB921398 breaks the shell shortcut menu".
--
Jim Barry, MVP (Windows SDK)
Jonathan Potter
I can't easily create a sample project although I could do this if it was
absolutely necessary. However, you can quite easily reproduce at least part
of the problem:
On a system that has KB921398 applied, run Notepad, select File/Open, and
browse to the Desktop folder. Then right-click on "My Documents". You will
find that no context menu appears. If you uninstall KB921398 and repeat
this, the context menu appears as normal.
Double-click on My Documents does work in Notepad, although it does not in
our software - but it seems logical to assume that it is the KB921398 is the
cause of both of these problems.
Thanks,
Jonathan Potter
""Jeffrey Tan[MSFT]"" <je...@online.microsoft.com> wrote in message
news:AMfqh2Ox...@TK2MSFTNGXA01.phx.gbl...
Aleksandr Tischenko
noticed the following: with KB921398 installed Explorer prevents access to
subfolders of namespace extensions that exposes SFGAO_FILESYSTEM flag for
folder items and uses ShellView created by SHCreateShellFolderView(Ex)
functions.
--
Aleksandr
""Jeffrey Tan[MSFT]"" <je...@online.microsoft.com> сообщил/сообщила в
новостях следующее: news:AMfqh2Ox...@TK2MSFTNGXA01.phx.gbl...
Jeffrey Tan[MSFT]
Thanks for your feedback.
Yes, I can reproduce this behavior. However, it is strange that after
uninstalling this hotfix, I still can not get the context menu to appear.
Additionally, based on my test on other 3 Win2003 SP1 machines, they all
have this problem. I will try to check if these problematic machines have
already installed KB921398.
I will help you to report this issue to our shell team. I will feedback any
progress here ASAP.
Jonathan Potter
Note that you need to reboot after removing the KB921398 hotfix. I just
tested this here on a virtual machine with XP SP2 and nothing else
installed, and after a reboot the context menu returned as expected.
Regards,
Jonathan Potter
""Jeffrey Tan[MSFT]"" <je...@online.microsoft.com> wrote in message
news:0KcZ0Qdx...@TK2MSFTNGXA01.phx.gbl...
WinAbility.Com
> Yes, I can reproduce this behavior.
Can you also reproduce the problem with the shortcut menus for the Zip files
caused by KB921398 that I've reported here a few days ago? Please ask the
shell team to look into it as well!
Thanks!
--
Regards,
Andrei Belogortseff
WinAbility(r) Software Corp. [ http://www.winability.com/ ]
"Useful Windows Utilities and Security Software"
Jeffrey Tan[MSFT]
Thanks for your feedback.
Oh, yes, you are right. Due to internal security policy, it seems my
machine has already got KB921398 installed, which I was not aware of, and
in my test, I re-install it again. So in uninstallation, I only removed one
copy of KB921398 and rebooted. There are still another copy of KB921398
working on my machine, that is why I am still experiencing the context menu
not appearing problem. After removing the second copy of KB921398 again and
reboot, I can get the context menu working now. Thank you for pointing this
out!
Yes, I am current working with our Shell team developers for this issue. I
have forwarded you and the community's concern to the Shell team, I will
continue monitor this thread and feedback any information here.
Devin Lamothe
are having the same problem in our organization regarding the My
Documents folder on the desktop not working correctly after this patch
being installed.
Uninstalling the patch does fix this issue, however the patch will just
get pushed out again through our SMS server.
Regards,
Devin Lamothe
Jeffrey Tan[MSFT]
Sorry for letting you wait.
Yes, our Shell team can reproduce this problem now. They confirmed this as
a bug in the hotfix. Below is the technical details and workaround for your
IShellBrowser application:
We try to prompt for all folder GUIDs right clicks and double-clicks in
untrusted zone.
The code path for double-click is handled mostly by comdlg32.dll itself and
so we don't reach the code where we are supposed to prompt.
But for context menu, comdlg32.dll falls back on defview code fully, and we
hit the code path where we try to prompt and we fail.
To workaround this problem, you can change _ZoneCheckMaybeHosted() to
return S_OK if it can't find the 2 interfaces
"IInternetHostSecurityManager" and "IInternetSecurityMgrSite". But that
will weaken security and expose shell to vulnerabilities from 3rd party
containers.
The other way to fix this is have an approved list of folder GUIDs which
shell trusts and have the function IsSelFolderGUID() return FALSE if the
folder GUID is known to be harmless [like Desktop, zip folders etc].
Any of the above 2 fixes should solve the problem for you. You can also
implement any of the 2 interfaces mentioned above in the same class which
implements IShellBrowser, and that might solve the problem too.
Our developer team has filed this bug in the internal database, and I think
they will continue work to resolve this problem. Hope the 2 workarounds can
resolve your problem. If you still have any concern or need any help,
please feel free to tell me, thanks!
Jonathan Potter
Thanks for that - it's good to know they have confirmed it as a bug!
I have tried adding IInternetHostSecurityManager and
IInternetSecurityMgrSite to my IShellBrowser implementation but they seem to
never be asked for by the shell.
Also, unfortunately I can't find any reference to _ZoneCheckMaybeHosted() or
IsSelFolderGUID() anywhere - not in MSDN, not in google, not even in the SDK
header files. Do you have any more information about where these functions
can be found?
Thanks,
Jonathan Potter
""Jeffrey Tan[MSFT]"" <je...@online.microsoft.com> wrote in message
news:1Wt$%23NyxG...@TK2MSFTNGXA01.phx.gbl...
Jeffrey Tan[MSFT]
Thanks for your feedback!
Yes, I have forwarded your concern to the Shell team. They are still
working on this bug now, and the workarounds they provided in last reply
are not tested at all. The right solution would be for you to get an hotfix
for this bug. You may contact Microsoft PSS for requesting the hotfix.
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at
http://www.microsoft.com/services/microsoftservices/srv_support.mspx.
Since this is a bug of Microsoft update, the supporting case of this hotfix
request will be free. Thanks for your understanding.