Windows 10 install fail (log below)

[xornand]

http://pastie.org/private/ksi2wx6i6rkiupv9l9smq

May be a permissions issue. Ran as an Administrator user, with UAC enabled.

https://i.imgur.com/lBfqXQw.png

Something to do with Squirrel...(though, I'm not quite sure with that is).

[xornand]

If I manually run the installer forced with elevated Admin privs, I can get the main thread to render it's form, but this pops up. https://i.imgur.com/9TsuKhy.png .. .. https://i.imgur.com/kF9inOp.png

[tgxn]

I have the same issue, attaching screenshot here, seems to do with Squirrel too.

[xornand]

I'm a win-dev, I'll try to get on it. I've localized the problem, but I need to do some chores before getting on it.

[cdokolas]

Duplicate of bug #14

[xornand]

Documenting my progress (edit: in this thread, I'm not sure what the social protocol dictates for dupes (i.e., should I close this and post in there? Right now I'm just using this thread to document the full Win port process, so it's not entirely relevant to bug #14 as the scope has broadened out))

My intentions are obviously to make this more ... crossplatform as it seems fairly OS X specific (see fsevents.Any windevs want to avoid problems here's what I've got so far.

1: VS 2015 Community edition SP3 from chocolatey. Formal suggestion: Since this is a free, fully capable toolset, we use this as the baseline standard to build against. 2: Python 2.7.x 32 bit installed to default dir. (Environment var's for PYTHON and/or junction links otherwise -- mklink C:\python27 "C:\Program Files (x86)\IDA 6.8\python"

On npm install an error is thrown npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12 fsevents is tied into OS X, workaround npm install --no-optionals

1. Within your shell "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\vsvars32.bat"
2. There's a bug in node-gyp for SP3, with a solution. https://github.com/nodejs/node-gyp/issues/949#issuecomment-224028256 Line 34: src/win_delay_hook.c

-PfnDliHook __pfnDliNotifyHook2 = load_exe_hook;
+const PfnDliHook __pfnDliNotifyHook2 = load_exe_hook;

Now I can get a 'mostly successful' build done (bound to :3000), but it's throwing an error [1] npm ERR! Failed at the felony@0.10.3 start-hot script 'cross-env HOT=1 NODE_ENV=development electron -r babel-register ./main.development'.

I don't know the ecosystem of node/npm/gulp/grunt/goop/whatevertheheck-I'm-too-old-to-keep-up-with-all-this which is why I'm not making leaps and bounds, but

[xornand]

This build is now 'successful' on Win10 Pro (Insider Developer Preview). None of the styling/theming/etc carried over, and I suspect it has something to do with the whole if (process.platform === 'darwin') { in main.development.js (obviously the darwin platform has way more of the styling implemented in it.

[frankcash]

This appears to be a duplicate issue of (#14)

[michaelpittino]

Is there any update on this issue? I really want to use felony on windows.

[TheChiefMeat]

Have the same issue, any progress on this being fixed?