Page 1 of 1
Recent dev builds: 'Please wait while Windows configures Explorer++'
Posted: Mon Feb 03, 2025 8:20 pm
by topbanana
Can't remember which was the last 'good' build, but the last few keep wanting to configure E++ when starting from scratch. And then sometimes when it's been running a while and i want to start another instance. But i can start many instances after the first one ok...
Strange af.
I've tried uninstalling all the e++ entries from Installed Apps (as they tend to build up), and reinstalling from scratch, but it still happens.
I haven't tried resetting all the settings though...
Any ideas?
Re: Recent dev builds: 'Please wait while Windows configures Explorer++'
Posted: Mon Feb 03, 2025 9:44 pm
by David Erceg
Hi topbanana, is this when using the installer?
Re: Recent dev builds: 'Please wait while Windows configures Explorer++'
Posted: Tue Feb 11, 2025 11:05 pm
by topbanana
Yes.
explorerpp_x64_setup.msi
I've installed a LOT of dev builds over the years... And this behaviour only started recently... I just can't remember which build started it.
I see the following:

Re: Recent dev builds: 'Please wait while Windows configures Explorer++'
Posted: Wed Feb 12, 2025 8:52 am
by David Erceg
The installer project hasn't had any substantial changes since 2018, so I'm not sure what's happening here.
Re: Recent dev builds: 'Please wait while Windows configures Explorer++'
Posted: Wed Feb 12, 2025 6:36 pm
by topbanana
Ok, after uninstalling every entry of E++ from Window's 'Installed Apps', i jumped back to an old build... 1.5.0.2487 and installed them one by one...
I think it's something to do with the shortcut it creates in the start menu and on the desktop.
When i got to 1.5.0.2540 it would cough up the above issue when started from the Start Menu, and then also from the desktop shortcut.
So i think that 1.5.0.2528 is the last know 'good' version.
If i create a shortcut to 'Explorer++.exe' in its Program Files folder, the 'old skool' way, and use that, it starts up just fine.
So i've added this direct shortcut to my Quick Launch Toolbar, and the workaround is working great for me!
It's a super odd issue... Never seen anything like this before.