Code::Blocks Forums

User forums => Help => Topic started by: crckdns on February 03, 2016, 12:14:59 am

Title: v16.01 won't start after fresh installation on win10 x64
Post by: crckdns on February 03, 2016, 12:14:59 am
I'm referring to the ticket: https://sourceforge.net/p/codeblocks/tickets/292/
I'm posting it here because Morten McFly said so.

After starting it (the launcher or directly the codeblocks.exe) with and without admin, the splash screen stays (if not disabled by /ns) forever. Process is also running without any activity.

Things I've done already:
creating empty default.conf in the app directory
tried packages: normal setup, mingw setup, nonsetup, nonadmin
tried parameters: /d /nd /ns  (is there any debug output? the parameter doesn't do anything it seems)
tried installing it on system C  and D partitions.
This is a fresh windows installation without any previous codeblocks installation. Last time I've used it, was the version 13 on windows 7.
Tried versions 13.12, 15.12RC, 16.01 - same effect - so it must be windows10 related I guess.

last activity before it stops doing anything (scanned with Process Monitor) attached.

Any idea what I can do guys?
Title: Re: v16.01 won't start after fresh installation on win10 x64
Post by: dmoore on February 03, 2016, 12:38:31 am
Have you tried --safe-mode? If it works, enable plugins one by one then quit and restart normally.
Title: Re: v16.01 won't start after fresh installation on win10 x64
Post by: crckdns on February 03, 2016, 12:42:44 am
wow ok, --safe-mode did indeed bring it behind the splash screen and it started.
Thanks a lot for this fast help! Now gonna search the faulty plugin..

edit: enabled all plugins again, started, it works. That makes not much sense right now, some hiccup?
Title: Re: v16.01 won't start after fresh installation on win10 x64
Post by: dmoore on February 03, 2016, 01:30:12 am
There was an old issue that would cause a crash/hang when C::B is updated from a very old version. Something to do with updating one or more config files. This workaround was the fix. It may be a similar issue for you, but it sounds like you installed on a clean system, which is worrying...