Skip to content

Windows Explorer has Win10 remnants + restarts entire "explorer.exe" process upon closing #233

Closed

Description

@SonicGamingTV2019

Before reporting your issue

  • My version of Windows is up to date (Atleast up to April 2024 as per update warning)
  • I'm running the latest version or the one prior of the Windows 10to7 Transformation Pack (I checked the changelog on the downloads page before opening the issue).

What version of Windows 10 are you using the transformation pack on?

Windows 10 Home 22H2 19045.7663

What version of the Transformation Pack are you having issues with?

Version 3.7

Summarise the issue

I don't know what happened, but starting this morning, Windows Explorer had very visible remnants of the Win10 Explorer instead of the Win7 one. The top bar is also not in dark mode, even though it was prior to today.

Another big issue I have is that every time I close Windows Explorer, it automatically restarts the entire "explorer.exe" process and I'm not sure why.

Screenshots

I can't upload screenshots for some reason, so I have attached a video of the issue instead.

https://files.catbox.moe/zd1g3n.mp4

How do you reproduce the bug/inaccuracy?

1: Open Windows Explorer
2: Close Windows Explorer
3: "explorer.exe" is restarted automatically

Expected behaviour

I expected Windows Explorer to be fully functional.

Additional Context

The restart happens every time I close Windows Explorer no matter what way I close it.

I re-installed the transformation pack twice (using the "Configure or update transformation" option), but it did not fix the issue.

Activity

  1. ImSwordQueen commented on Aug 13, 2026

    @ImSwordQueen
    Owner

    Check if pressing ESC when explorer loads (when startisback tells you) fixes the crashes. That will make it that SIB won't hook into explorer.

  2. SonicGamingTV2019 commented on Aug 13, 2026

    @SonicGamingTV2019
    Author

    By the time you sent that, I was already in the process of uninstalling then re-installing the pack.

    Reinstalling the pack did fix the issue though, so I guess I don't have anything to complain about anymore. If it does happen again though, I will use the method that you told me.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions