Skip to content

[Open-Shell & v4.4.196]: Fails to invoke CFD window when saving the .XML file (Open Shell Application > Menu Settings > Backup to XML) #2361

Closed

Description

@Michellehdr

Describe the bug

[Open-Shell & v4.4.196]: Fails to invoke CFD window when saving the .XML file (Open Shell Application > Menu Settings > Backup to XML)

Area of issue

Windows Explorer

To reproduce

  1. Deploy latest OS on X64 Machine. 
  2. Perform Windows and Store updates. 
  3. Download the Open-Shell application from vendor site.
  4. Install the “Open-Shell”application.
  5. Go to Settings of the application and enable show all settings
  6. Make changes to the settings
  7. Click on Backup Button > Save to XML File
  8. Observe, unable to see the explorer (the save as window can only be showed when clicking on taskbar)

Expected behavior

An explorer is opened to ask user to save the file

Open-Shell version

4.4.196

Windows version

Windows 11

Additional context

No response

Activity

  1. levicki commented on Jan 5, 2026

    @levicki

    For me neither save nor load work -- nothing happens. Windows 11 25H2, Open Shell 4.4.196.

  2. kalman7g commented on Jan 7, 2026

    @kalman7g

    2365 resolution also fixes this issue

  3. levicki commented on Jan 8, 2026

    @levicki

    2365 resolution also fixes this issue

    What is the resolution? Using vive tool to fiddle with features that get re-enabled automatically?

    That's not a resolution for file dialog not showing.

    The resolution is to no use Open Shell if the bug isn't fixed.

  4. Michellehdr commented on Jan 9, 2026

    @Michellehdr
    Author

    @levicki @kalman7g still could repro this bug after following steps in 2365

  5. levicki commented on Jan 9, 2026

    @levicki

    @levicki @kalman7g still could repro this bug after following steps in 2365

    Well count me out, I went back to Windows 10 and Classic Shell. That woks for me. Windows 11 is a piece of trash OS anyway.

  6. Rollback-Jockey commented on Jan 28, 2026

    @Rollback-Jockey

    I get it that the dev's blame this issue on a recent update... So why am i having zero other issued with my machines?

  7. added a commit that references this issue on May 12, 2026
    ddca898
  8. added a commit that references this issue on May 12, 2026
    b207064
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't working right.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions