Windows 10: Replace Common Item Dialog with legacy Common File Dialog window

I know this can be done and I do recall back in 2017 I was reading about this. However there is no possibility to know where exactly I found this two years back.

Just like title says, I want to replace common CIDs used post-Vista to open / browse / save file with older pre-2007 Common FIle Dialog Box (that one with places bar on it).

Below is the one I refer to. Its located under 1552 stylesheet in comdlg32.dll.mui and can be visible in older, typically cross-platform apps. Also visible when you export from regedit. I want all open / save dialog boxes to use this legacy common file dialog. This can be 100% done via registry hack. But I can not remember how exactly.

Anybody have any knowledge on how to do that? If you happen to know how to tell the system to use the legacy dialog box instead of common CIDs, do drop a note below.




:)

 

Save and Open common dialog

Hi

When I try to open or save file in my common dialog box always open ThisPc to show me the path. How to set it up to be closed. On my other computer ThisPc is always closed in an open or save dialog box.

many thx for help

 

32 bit common dialogs not working on 64 bit os


Running windows 10 64. Common dialogs on 32 bit applications do not work/appear.
First i thought there was only a problem with chrome, save dialog do not work/appear and i cannot download anything, unless you config chrome for autodownload. Then i realized that it was the entire system. 32 bit application common dialogs do not work. All 64 bit applications "open", "save" file dialogs work correctly. I cannot even open a project in Visual Studio 2015. I have installed chrome 64 and it works ok.
SFC didnt fix the problem, even after deleting common controls known files, such as comdlg32.dll, comctl32.dll from syswow64. With Process Explorer from Windows SysInternals, i have found that some 32 bit programs use comctl32.dll files from C:\Windows\WinSxS\x86_microsoft.windows.common-controls_... folders. I have not deleted them yet to see if sfc repairs them.

I have tried to reinstall windows 10 from usb but it does not work.

I have disabled all non microsoft applications and third party shell extensions from startup...nothing.
The only thing i have found to fix it is disabling visual themes in compatibility options (although windows 10 does not have this option, u can set the DISABLETHEMES flag in the registry, in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers). I thought it was the solution, Visual Sutdio works after 5 days yuhuuuu!!, but besides it ruins all the aspect of the application, i have found some other applications that still do not work, such as openiv, a GTA Editor, when i click on "Browse" to select the path for gta, the dialog does not appear.
I made a simple visual studio solution and when calling openfiledialog showdialog, it does not wait, it continues running to the next line code. Normally it opens the dialog and the program execution is "suspended" until user closes/accepts the dialog. Maybe it opens and closes immediately, i dont know, i have not been able to trace what happens after ShowDialog is called.
Five days googling the same sites and no solution. Disable Firewall, windows defender, onedrive (thinking that "old" applications do not expect to find an onedrive access in the open file dialog side panel), i do not have any other network drive, nothing works. It's the only thing that i am doing from 5 days ago, trying to fix it, seeing the same sites once and again, and it does not seem to be a common problem, or at least i am not searching properly.

 

32 bit common dialogs not working on 64 bit os

Running windows 10 64. Common dialogs on 32 bit applications do not work/appear.

First i thought there was only a problem with chrome, save dialog do not work/appear and i cannot download anything, unless you config chrome for autodownload. Then i realized
that it was the entire system. 32 bit application common dialogs do not work. All 64 bit applications "open", "save" file dialogs work correctly. I cannot even open a project in Visual Studio 2015. I have installed chrome 64 and it works ok.

SFC didnt fix the problem, even after deleting common controls known files, such as comdlg32.dll, comctl32.dll from syswow64. With Process Explorer from Windows SysInternals, i have found that some 32 bit
programs use comctl32.dll files from C:\Windows\WinSxS\x86_microsoft.windows.common-controls_... folders. I have not deleted them yet to see if sfc repairs them.

I have tried to reinstall windows 10 from usb but it does not work.

I have disabled all non microsoft applications and third party shell extensions from startup...nothing.

The only thing i have found to fix it is disabling visual themes in compatibility options (although windows 10 does not have this option, u can set the DISABLETHEMES flag in the registry, in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers). I thought it was the solution, Visual Sutdio works after 5 days yuhuuuu!!, but besides it ruins all the aspect of the application, i have found some other applications that still do not work, such as openiv, a GTA
Editor, when i click on "Browse" to select the path for gta, the dialog does not appear.

I made a simple visual studio solution and when calling openfiledialog showdialog, it does not wait, it continues running to the next line code. Normally it opens the dialog and the program execution is
"suspended" until user closes/accepts the dialog. Maybe it opens and closes immediately, i dont know, i have not been able to trace what happens after ShowDialog is called.

Five days googling the same sites and no solution. Disable Firewall, windows defender, onedrive (thinking that "old" applications do not expect to find an onedrive access in the open file dialog side panel),
i do not have any other network drive, nothing works. It's the only thing that i am doing from 5 days ago, trying to fix it, seeing the same sites once and again, and it does not seem to be a common problem, or at least i am not searching properly.