Hey @marcus
Firstly, thank you very very much for putting together the step-by-step guide - I think that’ll be very useful to many users.
Both really. We were initially trying with the windows installer as per this comment but have also been trying with an npm install alongside that windows installer incase it needed it to work properly.
Having started n8n via cmd/ps, everything works fine in the browser localhost:5678 - the issue lies in the windows installer throwing errors. Because almost every windows user (and therefore potentially substantial future revenue) will not be familiar with starting things via a windows flavoured cli like cmd or ps, this is why we were keen to get the export and import commands working in the Execute Command node of the windows installer version, whilst also allowing for alt-tabbing between windows.
Looking at the error from this previous comment, it would appear the windows installer version cannot find a module it needs under C:\Users\User\AppData\Local\Programs\n8n
I’m not too familiar with these things but as there is no ‘n8n’ file (without a filetype) in that directory, perhaps it needs to point to ‘n8n.exe’ like the other commands point to the respective cmd file.
I’m not sure if it’s just Jan or others that contribute towards the code and whether or not winning potential windows users are of any priority as I’m sure everyone has a very packed roadmap.
Thank you for sticking with us and for any other ideas you ‘might’ have at all.