Page 1 of 1
Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 17:59
by Jeeves
Latest beta of XY and this is the legitimate RTM Windows 7 Enterprise.
I don't know how many folders this affects, but this issue is that XY cannot seem to manage some system folders. They flat out don't match what Explorer shows and you cannot drag/drop between XY and Explorer, you cannot write to them, cannot really do anything in them at all, and the view that XY shows doesn't match what explorer shows at all, etc.

Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 18:20
by zer0
I'm upgrading to Windows 7, so this is of interest to me.
A quick noob-style question, but has to be asked: you do have "Show hidden files and folders" and "Show system files and folders" enabled in Tools -> Configuration -> General, don't you?
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 18:23
by Jeeves
zer0 wrote:I'm upgrading to Windows 7, so this is of interest to me.
A quick noob-style question, but has to be asked: you do have "Show hidden files and folders" and "Show system files and folders" enabled in Tools -> Configuration -> General, don't you?
Yes, Never run without those settings. I'm an IT SysAdmin.
Edit: I will say that for the most part I've run into very few places where this is of issue, but this folder doesn't seem to be touchable. I haven't poked around any to see what else isn't.
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 19:07
by zer0
This issue does not occur on my Vista system, but I believe that folder is present on XP as well, so hopefully we can test it on that OS too.
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 19:31
by serendipity
I am also on Windows 7 Ultimate at my work since yesterday and I can access that folder alright with XY. I turned UAC completely off.
Screenshot below shows XY on left and and Explorer on the right. I dont see any difference here, including number of files and size etc.

Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 19:52
by TheQwerty
My first thoughts are it's either:
1) Permissions related - Are you running XY as administrator?
2) WOW64/x64 related - What architecture is this system? Do you have WOW64 Redirection enabled? (View->Show Items->WOW64 Redirection)
I'm stuck on XP here at work, so I can't really check it out.
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 19:59
by zer0
TheQwerty wrote:2) WOW64/x64 related - What architecture is this system? Do you have WOW64 Redirection enabled? (View->Show Items->WOW64 Redirection)
I think that's enabled by default and it's not possible to disable it.
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 20:13
by TheQwerty
zer0 wrote:TheQwerty wrote:2) WOW64/x64 related - What architecture is this system? Do you have WOW64 Redirection enabled? (View->Show Items->WOW64 Redirection)
I think that's enabled by default and it's not possible to disable it.
On a 32-bit system that's the case, but on a 64-bit one you can disable it, %windir%\system32 is one of the paths that gets redirected.
I posted a tip showing how you can access both the 32- and 64-bit system32's without disabling WOW64 redirection:
http://www.xyplorer.com/xyfc/viewtopic.php?f=3&t=3833
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 23:07
by noir
its caused by wow64, since i just tested.
to disable wow64 go to - View - Show Items - wow64 redirection
Re: Windows 7 - secure folder is unmanagable
Posted: 14 Aug 2009 23:19
by Jeeves
TheQwerty wrote:My first thoughts are it's either:
1) Permissions related - Are you running XY as administrator?
2) WOW64/x64 related - What architecture is this system? Do you have WOW64 Redirection enabled? (View->Show Items->WOW64 Redirection)
I'm stuck on XP here at work, so I can't really check it out.
It is 64-bit, I should have put that in my post. I apologize for not having done so. I am no longer at work but will check the redirection.
Neither XY nor Explorer is being called explicitly as "Run as Administrator". UAC has been set to the lowest level of prompting via the Windows 7 Action Center, but beyond that no modifications to registry or the like to disable it.
Re: Windows 7 - secure folder is unmanagable
Posted: 15 Aug 2009 01:06
by TheQwerty
Jeeves wrote:It is 64-bit, I should have put that in my post. I apologize for not having done so. I am no longer at work but will check the redirection.
This is very likely the case then as XYplorer is a 32-bit app, and Explorer is 64-bit.
So when you access "%windir%\System32"...
In Explorer you actually get "%windir%\System32" (64-bit).
In XY with WOW64 Redirection Enabled you actually get "%windir%\SysWOW64" (32-bit).
In XY with WOW64 Redirection Disabled you actually get "%windir%\System32" (64-bit).
If you create "%windir%\Sysnative" (you must use Explorer to do this) then you can leave WOW64 Enabled in XY and use:
"%windir%\Sysnative" to access "%windir%\System32"
and
"%windir%\System32" (or "%windir%\SysWOW64") will still redirect to "%windir%\SysWOW64".
Note that using Sysnative will only do this in 32-bit apps, it will look empty to 64-bit ones.
Re: Windows 7 - secure folder is unmanagable
Posted: 15 Aug 2009 02:22
by Jeeves
I'm sure I missed a checkbox or post suggesting I do this but I will say that it's bothersome that the app doesn't have a catch for such a condition.
Re: Windows 7 - secure folder is unmanagable
Posted: 17 Aug 2009 19:19
by Jeeves
"WOW64 Redirection" was enabled. Checking both "SysWOW64\oobe" and "System32\oobe" both looked identical to the picture I posted that had too few files. Only browsing to the Explorer created "Sysnative" allowed me to view the actual folder.
Re: Windows 7 - secure folder is unmanagable
Posted: 12 Dec 2010 15:03
by w64bit
@ XYplorer
Is it possible to give us an x64 version of XYplorer in order to fix this and also x64 shell extensions (like for WinRAR x64 which doesnt working as suppose)?
Thanks
Re: Windows 7 - secure folder is unmanagable
Posted: 12 Dec 2010 15:07
by admin
A 64-bit version is planned but will not come very soon.
What's the specific problem you have? There might be a workaround...