Windows 10, TC8.52b1 - Files\Folders Properties Desktop Err
Moderators: Hacker, petermad, Stefan2, white
Windows 10, TC8.52b1 - Files\Folders Properties Desktop Err
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]
[Window Title]
Desktop
[Content]
The properties for this item are not available.
[OK]
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
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.
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
https://www.ghisler.com
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.
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.
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
How do you do that on Windows 10? I couldn't find any options in the context menu or properties, only "As administrator".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.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
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
https://www.ghisler.com
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.
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.
- Alpengreis
- Junior Member
- Posts: 10
- Joined: 2014-01-07, 16:02 UTC
- Location: Switzerland, SO
@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
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
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.
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.
- Alpengreis
- Junior Member
- Posts: 10
- Joined: 2014-01-07, 16:02 UTC
- Location: Switzerland, SO
[SOLVED]
Dear friends!
For Fix delete reg:
also check this records:
Cheers
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"
Re: [SOLVED]
Warning!Man4red wrote:Dear friends!
For Fix delete reg:
CheersCode: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{448aee3b-dc65-4af6-bf5f-dce86d62b6c7}] "Runas"=-
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.
- Alpengreis
- Junior Member
- Posts: 10
- Joined: 2014-01-07, 16:02 UTC
- Location: Switzerland, SO
Why not? I see the same.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
"DllSurrogate" you can leave as is - nevermind
"RunAs" need to be deleted
Code: Select all
"Runas"=-
Default value is "Interactive User" (correct)
That is it