Windows 10, TC8.52b1 - Files\Folders Properties Desktop Err

Please report only one bug per message!

Moderators: white, Hacker, petermad, Stefan2

asukhov
Junior Member
Junior Member
Posts: 3
Joined: 2015-08-19, 10:20 UTC

Windows 10, TC8.52b1 - Files\Folders Properties Desktop Err

Post by *asukhov »

Windows 10, TC8.52b1 - Files\Folders Properties not working - Desktop error appear:

[Window Title]
Desktop

[Content]
The properties for this item are not available.

[OK]
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48083
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Unfortunately I cannot reproduce it, sorry. I tried with normal user rights and higher elevated rights. Both the context menu and Alt+Enter work fine. Maybe it's caused by a context menu extension (shell extension) which is incompatible with Windows 10?

Btw, another user has reported this too: It seems to happen also in other programs, like the "Open" dialog in notepad.exe.
Author of Total Commander
https://www.ghisler.com
asukhov
Junior Member
Junior Member
Posts: 3
Joined: 2015-08-19, 10:20 UTC

Post by *asukhov »

When start TC in user session - no problem - all work fine (normal user and high elevated rights).

But when start TC like a different user (for example USER2) from the USER1 session - nothing works: when press Alt+Enter no windows apper at all.

When start TC with Run As Administrator with credentials of USER2 in USER1 session and try Alt+Enter - Destop Error appear.

I try to disable all non-Microsoft Shell Extensions (using ShExView, with reboots) but nothing changed.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48083
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

But when start TC like a different user (for example USER2) from the USER1 session - nothing works: when press Alt+Enter no windows apper at all.
How do you do that on Windows 10? I couldn't find any options in the context menu or properties, only "As administrator".
Author of Total Commander
https://www.ghisler.com
asukhov
Junior Member
Junior Member
Posts: 3
Joined: 2015-08-19, 10:20 UTC

Post by *asukhov »

:) Right-click with Shift on TOTALCMD64.EXE
Or Right-click on TC shortcut -> Press and hold Shift and right-click on Total Commander -> Run as different user
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48083
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I see it now - indeed the same happens with notepad.exe ("Save as" dialog), while it works in Windows 7 and 8.1. I have reported it as a bug to Microsoft. I don't think that there is anything I can do to handle that.
Author of Total Commander
https://www.ghisler.com
kstanush
Junior Member
Junior Member
Posts: 3
Joined: 2015-09-08, 16:45 UTC

Post by *kstanush »

I too reported this issue to Microsoft last week, but have not heard back yet. This problem only affects Windows 10, and only when running an application as another user (including admin). This error will be displayed in any application that interacts with the Explorer context menu and presents the 'Properties' option.

It can be duplicated by just running Notepad as a different user, saving a file, and right clicking on any existing file or directory and selecting the 'Properties' option.
User avatar
Alpengreis
Junior Member
Junior Member
Posts: 10
Joined: 2014-01-07, 16:02 UTC
Location: Switzerland, SO

Post by *Alpengreis »

@ghisler(Author)

Mybe it has to do with the following aspect ...

http://answers.microsoft.com/en-us/windows/forum/windows_7-security/i-get-error-msg-saying-the-properties-of-this-item/abdee602-354e-4816-b646-62ae1243b367

If yes, can you, Christian (or someone else), check, if this fix is good for Windows 10 (attention for different architectures 32/64 bit and versions) too (unfortunately, I am not good enough with such regedit things)?

Regards!
Alpengreis
kstanush
Junior Member
Junior Member
Posts: 3
Joined: 2015-09-08, 16:45 UTC

Post by *kstanush »

Microsoft confirmed to me last night that this was a bug in Windows 10, but as usual, no commitment to fix it or when.

I too saw this registry 'fix' for this problem on earlier o/s, but suspect that it is not related, and even if it did fix the issue, an ISV with an application with this problem can't really use this fix on a customer's installation anyway.
User avatar
Alpengreis
Junior Member
Junior Member
Posts: 10
Joined: 2014-01-07, 16:02 UTC
Location: Switzerland, SO

Post by *Alpengreis »

Ah, okay, very good to know. Thank you for clarification, kstanush!

EDIT: I had analyzed the keys a bit, it seems it has nothing to do with THIS problem ... sorry for the noise!
Man4red
Junior Member
Junior Member
Posts: 3
Joined: 2015-10-13, 13:01 UTC

[SOLVED]

Post by *Man4red »

Dear friends!
For Fix delete reg:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{448aee3b-dc65-4af6-bf5f-dce86d62b6c7}]
"Runas"=-

also check this records:

Code: Select all

[HKEY_LOCAL_MACHINE\software\Classes\Interface\{B0371994-3FA6-4AB5-BD72-B3479FE90894}]
@="IPropertySheetHandler"

[HKEY_LOCAL_MACHINE\software\Classes\Interface\{B0371994-3FA6-4AB5-BD72-B3479FE90894}\ProxyStubClsid32]
@="{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}"

[HKEY_LOCAL_MACHINE\software\Classes\CLSID\{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}]
@="PSFactoryBuffer"

[HKEY_LOCAL_MACHINE\software\Classes\CLSID\{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}\InProcServer32]
@="C:\\Windows\\System32\\ActXPrxy.dll"
"ThreadingModel"="Both"
Cheers
User avatar
Stefan2
Power Member
Power Member
Posts: 4158
Joined: 2007-09-13, 22:20 UTC
Location: Europa

Re: [SOLVED]

Post by *Stefan2 »

Man4red wrote:Dear friends!
For Fix delete reg:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{448aee3b-dc65-4af6-bf5f-dce86d62b6c7}]
"Runas"=-
Cheers
Warning!

never delete maybe important registry keys just on suspicion.

Always double check by an internet research,
and best firstly just rename the key, e.g. to "...AppID\__{448a..."
to disable it, instead of quickly delete it.



Sorry Man4red, no offend to you. Just an general remark.
Man4red
Junior Member
Junior Member
Posts: 3
Joined: 2015-10-13, 13:01 UTC

Post by *Man4red »

Of course make "Export" or other backup before changing registry.
This solution 100% worked and tested by me and provided "AS IS", without warranty of any kind

TC Ver: 8.51a 32bit
Win 10 Ent x64 Eng (build 10240)
User avatar
Alpengreis
Junior Member
Junior Member
Posts: 10
Joined: 2014-01-07, 16:02 UTC
Location: Switzerland, SO

Post by *Alpengreis »

The keys to check are all okay ... but then:

The key to delete have NOT the same data, as you can see ...

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{448aee3b-dc65-4af6-bf5f-dce86d62b6c7}]
"DllSurrogate"=""
"RunAs"="Interactive User"

And now?

Win 10 Pro x64 - ((Swiss) German Edition).

Greetings
Man4red
Junior Member
Junior Member
Posts: 3
Joined: 2015-10-13, 13:01 UTC

Post by *Man4red »

Alpengreis wrote:The keys to check are all okay ... but then:

The key to delete have NOT the same data, as you can see ...

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{448aee3b-dc65-4af6-bf5f-dce86d62b6c7}]
"DllSurrogate"=""
"RunAs"="Interactive User"

And now?

Win 10 Pro x64 - ((Swiss) German Edition).

Greetings
Why not? I see the same.
"DllSurrogate" you can leave as is - nevermind
"RunAs" need to be deleted

Code: Select all

"Runas"=-
BTW this code "-" means that key "Runas" must be deleted when it's in *.reg files
Default value is "Interactive User" (correct)


That is it
Post Reply