Ok so either win 10 changed the location for appdata, or lazarus is not creating its config.
try
lazarus --primary-config-path=D:\laz_conf
replace D:\laz_conf with a folder that is writable to everyone.
See if any files are created in there.
-----------
What happens if you run (in the lazarus directory)
lazbuild.exe --build-ide="-O- -gw -Criot -Sa"
you need to open a console for that.
It should take a while, and rebuild the IDE. Test the new one.
(If this works you may skip the download in the next part, as the rebuild IDE will have console-output and debug info. (Though the download has some added bugfixes, as it is from a newer code base)
-----------
I uploaded a build of the 1.8 fixes branch (only Lazarus.exe / 32 bit) to
http://www.friebe-net.de/lazarus.exeThis is build with console output. If you open it, it should open a console window (black msdos like text), on which (hopefully) there should be some output.
It is also a good deal bigger (200MB), as it contains debug info.
You can scan the file prior to using:
https://virustotal.com/(scan url, the file is to big for upload)
You can scan the file online after striping debug info. Make a copy and in your lazarus folder run
fpc\bin\i386-win32\strip.exe lazarus-copy.exe
Also at
https://www.metadefender.com/#!/scan-fileCopy the file into your lazarus dir, and run it there.
-----------
as for gdb you can try attach once it hangs.
Start Lazarus (just the normal way, or with --primary-conf.... option)
Again start gdb with
.\mingw\i386-win32\bin\gdb.exe .\lazarus.exe
Use the windows task manager, to get the PID of the hanging lazarus.
In gdb type
attach 1111
(where 1111 is the PID)
then
t 1
bt
and all the rest from my previous gdb post.