Windows 10 Folders Problem

from Stardock Forums

For me, all apps launch fine with Objectdock on Windows 10. However, there is a bug when you try to launch a folder. The folder initially opens up for a second and then disappears, only to then reappear a second later. Doesn't happen for folders that are already open on the desktop.

Nexus Dock also has a similar issue. Maybe something needs to be updated to be compatible with Windows 10. Folders launched from Windows taskbar don't have this problem.

objectdock
15,979 views 11 replies
Reply #1 from WinCustomize Forums Top

I haven't seen that one yet, I'll check it out when I get back home from the weekend.

However, if this is true for all systems, it sounds more like a bug in Windows 10 than a compatibility problem. Furthermore, if the folder opens anyway, its not a serious issue, right?

Reply #2 from Stardock Forums Top

Not a deal-breaker at all but it does come across like something isn't working right! Folders open alright. Likely a Microsoft bug but hope it gets fixed soon!

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from WinCustomize Forums Top

Ok, I just tried it on a Windows 10 system and I see no such problem.

My guess is that this is something specific to your system, sorry.

Reply #5 from Stardock Forums Top

The ONLY way I managed to fix this was with a dreaded complete reinstall of Windows 10. I had previously upgraded my version of Windows so must be some incompatibility glitch.

 

Mind you, still having the file explorer thumbnail preview problem so comes across like ObjectDock hasn't been exhaustively tested with Windows 10 with a large test group. Hoping the team look into this a bit more.

Reply #6 from Stardock Forums Top

Actually this is a know issue with Windows 10 completely unrelated to Object dock.

 

If you go into the Folder-->View-->Options-->View Tab-->

you need to turn off the "Launch Folder Windows in Separate Process" option

 

This will stop the double flash when opening the folders.

 

E-

Reply #7 from WinCustomize Forums Top

Quoting lordgoderic, reply 6

Actually this is a know issue with Windows 10 completely unrelated to Object dock.

 

If you go into the Folder-->View-->Options-->View Tab-->

you need to turn off the "Launch Folder Windows in Separate Process" option

 

This will stop the double flash when opening the folders.

 

E-
End of lordgoderic's quote

 

That option should be unchecked by default, at least mine is.

Reply #8 from Stardock Forums Top

Just installed Windows 10, so looking for fixes to the graphics.

The folder icons cut off the folder content so that the files inside are only partially recognizable.  I was told this was normal for Windows 10.  Windows Vista, 7, and 8.1 displayed the folder content well in the icons.  Has anyone else had this problem?

Does Stardock have a program to bring back the Windows 7 folders so that the content displays properly?

 

Thank you.

Reply #9 from Stardock Forums Top

Thank you, but I'm referring to the Windows 10 folder icon itself and do not yet have Stardock -- that's why I'm considering it, but want to make sure it will fix the problem.  Any ideas? ( It's hard for me to distinguish between the folders if I can't see the thumbnail colors inside.)

Reply #10 from WinCustomize Forums Top

Gwendolyn1265, the only Stardock product that might would fix that would be IconPackager, and it is not supported on Windows10.

Reply #11 from Stardock Forums Top

That's it, Redneckdude!  I used to have IconPackager for Windows XP and had fun with it then, but had forgotten it was a separate product.  Thanks for reminding me!

Also, on the "flash" question mentioned above, does that refer to the problem with the folder staying at the point at which we've scrolled down to find a file?  I might have to uninstall Win10 because of that -- the folder leaps back to the top of the window before I can select the file I want to edit. (It just started that tonight after earlier icon problem post. I'm told it might have to do with wallpaper shuffle changes, which would really be a strange bug!  -- Any ideas?

Thank you!