MS developer network

I have a node.js express4 app that has been running on a previous version of windows 10 iot - some version less than 15063. My sd card died so I had to re-image the pi to the latest build - 10.0.15063. Now when I try to run my express app on
the rpi via visual studio 2015, it does not start. I see "deploy succeeded" then "The program '[0x2A4] backgroundTaskHost.exe' has exited with code 1 (0x1)."
In the rpi file system I see that the package is mostly loaded, although I don't see any files under the LocalState directory and that is where the node.js application is loaded when it works correctly. Any ideas on this? I did manage to get
past the VCLibs not loading correctly by running another C# program on the rpi successfully.
I have searched this forum and found things that could be related but are not exactly the same.
Any help appreciated.
Jim

Hi Jim,
Can you try the steps for the Node js sample app? (https://developer.microsoft.com/en-us/windows/iot/samples/expressnodejs) Maybe there is a configuration step
you missed on the new image?
Sincerely,
IoTGirl

I seem to be making some progress with this. I uninstalled all the copies of 'Node.js Tools for UWP Apps' and then reinstalled the latest versions - 1.5.7 for visual studio 2017 and 1.5.5 for vs 2015 ( not sure why this doesn't say 1.5.6, since it
looks like that is the most recent version for vs 2015.)
Anyway after doing this, deploying my node application to the raspberry pi works again on vs 2015. It copies all of the files and populates the LocalState directory as before with the files for the web site.
However now I get an access violation as node.js starts up:
Unhandled exception at line 234, column 9 in Unknown script code (1)
0x800a1624 - JavaScript runtime error: Reflect.apply: argument is not an array or array-like object
Is this a known problem? Any suggestions?
I tried running the sample as you indicated above, but it causes vs 2017 to access violate and close every time I run it, right after it says 'Deploy Succeeded'. However I would be happy just to get the vs 2015 version of my code running again.
Jim

I found a related thread.
https://social.msdn.microsoft.com/Forums/en-US/c5188d26-b5c4-459c-8844-5661fb277e0e/nodejsdebugging-the-program-3092-backgroundtaskhostexe-has-exited-with-code-1073741189?forum=WindowsIoT&prof=required
Near the bottom of this thread the same problem that I am seeing shows up. It looks like the fix is to try a different version of windows. I tried the most recent Inside Preview, 16193 but the problem still exists.
I can't see any older builds than 15063 in the IoT Dashboard. I haven't figured out how to install an older version...
Jim

Hi Jim,
The "Older Build" is actually the release build. Just choose the one that is not insider and you should have the correct binary.
Sincerely,
IoTGirl

The other build available with the IoT Dashboard is 15063 and that build has the same problem in it. I either need an older build than 15063, or a newer build than 16193 that actually has the fix in it. It looks like munyirik was working on a
fix, from this https://github.com/ms-iot/node/pull/14 but I don't see a completion date.
Can you tell me if this is fixed somewhere that I can access? Or can I access an older build than 15063?
thanks
Jim 

I managed to find build 14393 at this url:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=53360
I downloaded this iso and flashed my sd card with it. Now I am back up and running with this older build. Node.js /express work just fine on this build. ( in case someone else has run into this problem ).
Is there any way to tell when this issue will be fixed in newer builds?
Jim