file explorer set to 'open each folder in same window' but a fresh window opens

On my Windows 10 Pro 64 bit (1703) system I have two weird problems. I have file explorer set to 'open each folder in same window' but a fresh window opens most of the time, some times 2! I have been thinking it was a mouse problem with some kind of double click but using a separate usb mouse has the same problem. Just trying to get to a sub folder leaves me with lots of open explorer windows each one level  higher than the next,


Does any body have any thought on these?

In Options - click on the "View" tab. Uncheck "Launch folder windows in a separate process".

Does that solve the problem?

Thanks for the suggestion, I wish it was that simple, I have toggled that setting many times to no  good result. This problem has existed back to ver 1511. I am getting very frustrated with this.

I have been looking at this problem again and have additional observations:

When I start explorer  form the run box the opening of a new window only seems to happen when I try to go to the first subfolder and then does not seem to be opening a new window. I have been using a shortcut from 'quicklaunch' toolbar (C:\WINDOWS\explorer.exe /e, /select, h:\Temp) using this shortcut has the aforementioned problem. I am still perplexed and seeking a resolution.

It's difficult to tell from your post, but in the startup command you use make sure there are no spaces after the commas.

There were spaces now there are not but no change.

To always open each folder in the same window execute attached registry file.

Thanks freebooter

I am still searching for documentation on the various values in that key. Do you have a link/ref??

I would like you to check the system integrity of your Windows OS installation.

• Please type cmd.exe into Start Menu search box.
• Please right click cmd.exe and select "Run as administrator".
• Please type the following command and press the <Enter> key: sfc /scannow (Please note that there is a space between 'sfc" and "/scannow".)
• It should take about 20 minutes to run, if there are no serious errors.
• If the System File Checker reports that some errors were fixed, but some remain; please reboot your computer and run the System File Checker from an Administrator Command Prompt, again.
• If the System File Checker again reports that some errors were fixed, but some remain, please reboot your computer and run it a third time.
• If "Resource Integrity Violations" (errors) are reported that could not be corrected, or were not corrected after a third SFC run, then please navigate to the folder: C:\Windows\Logs\CBS and copy the file "cbs.log" to your desktop immediately. I am asking you do that because that file is dynamic, so I want to be able to examine a copy that is unchanged from the time that the System File Checker was run.
• If there are errors that couldn't be corrected, let me know and I will provide you with instructions as to how to upload the file

Not a bad idea, I will start that now.

A lot of these

 

017-10-25 18:39:59, Info                  CSI    00004c5f [DIRSD OWNER WARNING] Directory [l:119]'\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCResources\MSFT_UserResource\en-US' is not owned but specifies SDDL in component Microsoft.PowerShell.DSCResources.Resources, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-10-25 18:39:59, Info                  CSI    00004c60 [DIRSD OWNER WARNING] Directory [l:122]'\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCResources\MSFT_ServiceResource\en-US' is not owned but specifies SDDL in component Microsoft.PowerShell.DSCResources.Resources, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}    

 

2017-10-25 18:40:39, Info                  CSI    00005ae7@2017/10/25:22:40:39.618 Primitive installers committed for repair
2017-10-25 18:40:39, Info                  CSI    00005ae8@2017/10/25:22:40:39.633 Primitive installers committed for repair
2017-10-25 18:40:39, Info                  CSI    00005ae9 [SR] Verify complete
2017-10-25 18:40:39, Info                  CSI    00005aea [SR] Repairing 0 components
2017-10-25 18:40:39, Info                  CSI    00005aeb [SR] Beginning Verify and Repair transaction
2017-10-25 18:40:39, Info                  CSI    00005aec [SR] Repair complete
 

Ending in the above. If the whole file might be a help I will u/l it.

Open Command Prompt as a administrator and execute following command.

Dism  /Online  /Cleanup-image  /Restorehealth

Did that, problem persists.

Thanks for you help Frebooter!

I have also tried

:: 32 bit and 64 bit
IF EXIST "%SystemRoot%\System32\actxprxy.dll" "%SystemRoot%\System32\regsvr32.exe" "%SystemRoot%\System32\actxprxy.dll"
IF EXIST "%ProgramFiles%\Internet Explorer\ieproxy.dll" "%SystemRoot%\System32\regsvr32.exe" "%ProgramFiles%\Internet Explorer\ieproxy.dll"

:: 64 bit only (32bit on 64 bit)
IF EXIST "%WinDir%\SysWOW64\actxprxy.dll" "%WinDir%\SysWOW64\regsvr32.exe" "%WinDir%\SysWOW64\actxprxy.dll"
IF EXIST "%ProgramFiles(x86)%\Internet Explorer\ieproxy.dll" "%WinDir%\SysWOW64\regsvr32.exe" "%ProgramFiles(x86)%\Internet Explorer\ieproxy.dll"

As seen on some web site for a seemingly similar problem.

BTW Freebooter you never answered my question in  #8 :I am still searching for documentation on the various values in that key. Do you have a link/ref??

Thanks for you help

You are very welcome.

I don't have link i can give you!