none
Build of Windows CE 7 Platform Builder immediately fails on Win 10 x64 system RRS feed

  • Question

  • I have been documenting the process of preparing, installing and building Windows Compact Embedded 7 for use with VS 2008.

    Thus far the process was followed on a Win 7 x64 system, and with only a little effort the Platform Builder worked just fine.

    I followed exactly the same process on a Win 10 x64 system.  Only the Windows OS is different.

    Whenever I try and build the solution in VS 2008 it immediately fails with the following error:

    PBSpawn: Error: Current process is running in a job that does not allow breakaway. Unable to create child process in new job.

    There is nothing in the Event Viewer.

    I've turned off UAC; firewall; granted full permissions to the C:\WinCE700 folder, VS 2008 folder and the MS Platform Builder. No joy.

    This error is not listed anywhere on the internet.  It reeks of a permission problem, but there's little else I can do to grant any extra permissions to any folders, users, anything.  My IT team can't think of what other permissions might be required, but is suspicious that this is the real problem.

    Can someone please advise what this error means and suggest how to fix it? Please.

    Thanks,

    Dave

    Tuesday, April 30, 2019 6:25 PM

Answers

  • Hi Michel,

    I have some good news.

    I was planning on uninstalling each Windows (Security) Update one after the other; rebooting; then trying the CE 7 build using VS2008 on each pass.  However, after the most recent update was uninstalled and the system restarted there was a new update installed.  Since updates are being forced onto the PC beyond my control, I tried the CE build and lo-and-behold it started. :)

    The Win 10 x64 PC is running build 17763.404 - Version 1809.
    Removed Windows update:  KB4490481 2-May-19.  (It's unknown if just this was the root cause)

    Windows update that appears to fix the problem:  KB4476976, 3-May-19

    Update:  Just to be sure I reinstalled KB4490481; Reboot; Run CE Build - PBSpawn error - FAIL

    Uninstall KB4490481; Reboot; Run CE Build - SUCCESS.

    Conclusion:  The error appeared long before KB4490481 was installed (yesterday).  So there's more dynamic to this than meets the eye.  Perhaps a combination of the two aforementioned updates that resolves this issue.

    I sincerely hope that my efforts help out others. Thank you so much for your help. 

    Best regards,

    Dave


    Friday, May 3, 2019 3:46 PM

All replies

  • This happens when running Windows 10 v10.0.17763.379 and you have the KB4493509 update installed. Removing KB4493509 fixes the issue.

    This has been reported to Microsoft, hopefully a fix will be released shortly.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, April 30, 2019 11:03 PM
    Moderator
  • Hi Michel,

    Thank you so much for your informative post.  It was a huge surprise to find out that others are aware of this error and that it has been reported to MS.

    Could I reach out to you for a little more help on this same topic.

    The Win 10 x64 PC is running build 17763.404 (not .379) and the KB that you mentioned is not installed.

    However, there is a KB4493510 installed. 

    My research yesterday did not suggest that these two updates share any fixes, just because they were released with consecutive numbers.

    I'm loathe to try and randomly uninstall Windows updates because our Corp IT Group Policy will almost certainly try forcing them back onto the system.

    Could you please shed some light on any other updates that might be the root cause of the PBSpawn error?

    TIA and regards,

    Dave

    P.S. I have stumbled upon the guruce.com blogs and they are a great source of information. Excellent stuff!

    Thursday, May 2, 2019 1:35 PM
  • Dave,

    This issue was first reported by a Toradex customer on their forum. The issue was reproduced by Toradex. I can't reproduce the issue because my PC does not offer me KB4493509.

    My Win10 version is 10.0.17134. The last update that was offered and installed is KB4493437 (and Windows Update check says no further updates available) and I have no issues at all building WEC7 kernels (and neither any problems building WEC2013 kernels).

    All I can suggest is to open a support request with MS to give it a push...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, May 2, 2019 8:45 PM
    Moderator
  • Hi Michel,

    I have some good news.

    I was planning on uninstalling each Windows (Security) Update one after the other; rebooting; then trying the CE 7 build using VS2008 on each pass.  However, after the most recent update was uninstalled and the system restarted there was a new update installed.  Since updates are being forced onto the PC beyond my control, I tried the CE build and lo-and-behold it started. :)

    The Win 10 x64 PC is running build 17763.404 - Version 1809.
    Removed Windows update:  KB4490481 2-May-19.  (It's unknown if just this was the root cause)

    Windows update that appears to fix the problem:  KB4476976, 3-May-19

    Update:  Just to be sure I reinstalled KB4490481; Reboot; Run CE Build - PBSpawn error - FAIL

    Uninstall KB4490481; Reboot; Run CE Build - SUCCESS.

    Conclusion:  The error appeared long before KB4490481 was installed (yesterday).  So there's more dynamic to this than meets the eye.  Perhaps a combination of the two aforementioned updates that resolves this issue.

    I sincerely hope that my efforts help out others. Thank you so much for your help. 

    Best regards,

    Dave


    Friday, May 3, 2019 3:46 PM
  • Based on the threads found, this error occurs across multiple Windows 10 builds, and it seems that the Windows 10 build paired up with a specific KB Windows Update causes the error. In my case it was Windows 10, build 10.17763.465, paired up KB 4495667. Removing Windows Update KB 4495667 allowed getting past the "PBSpawn: error: Current process is running in a job that does not allow breakaway. Unable to create child process in new job."

    (Please see https://social.msdn.microsoft.com/Forums/office/en-US/183cd348-48d2-42f5-9061-de58e11bf97e/windows-1017763465-platform-builder-no-longer-works?forum=winembplatdev&prof=required.)

    I am also trying to reach out to MS through our distributors, as this error needs an official MS fix, and not have to rely on uninstalling KBs based on trial and error, especially for production quality code.

    Updating this post with your latest finding will help everyone, as the error is so recent.

    Monday, May 13, 2019 3:56 PM
  • Hi, thank you for building this thread. It is good to know somebody has the same troubles...I am experiencing the same issue with WEC2013 platform builder and Win 10 x64.

    First time I detected the problem after KB4493509 installation. When removed the update, the PB worked OK.

    It reappeared with KB4495667 and uninstall helped as well. Yesterday, KB4494441 installed twice and problem appears again. Current build is 17763.503, version 1809.


    • Edited by Milan416 Thursday, May 16, 2019 7:55 PM
    Thursday, May 16, 2019 7:54 PM
  • I've been able to reproduce the issue also on VS2015 + WEC2013, on Windows 10 Pro x64, 10.0.17763, Build 17763.

    I had to uninstall both KB 4493509 and KB 4495667. Just uninstalling one of those doesn't fix the issue. Only uninstalling both gets me past the "PBSpawn: error: Current process is running in a job that does not allow breakaway." error.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6


    Saturday, May 18, 2019 5:05 AM
    Moderator
  • WORKAROUND (found by MVP Minsung Kim):

    1. Apply all updates (do not uninstall any)
    2. Run Visual Studio 2015 and open your WEC2013 OS Design -or-
      Run Visual Studio 2008 and open your WEC7 OS Design
    3. Build your OS Design
    4. If it builds; hooray, all good! If it doesn't, continue below:
    5. Click Start -> Restart to reboot your machine
    6. When Windows 10 comes up again, it will automatically start VS and load your OS Design.
    7. Now build your OS Design
    8. It should build just fine.

    Next time you reboot your PC (without VS running), you will get the PBSpawn error back, so this is definitely not a solution but just a temporary workaround until Microsoft releases another update that fixes the problem for good.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6



    Sunday, May 19, 2019 8:36 PM
    Moderator
  • Microsoft is working on a resolution and will provide an update in an upcoming release, but knowing how many people are affected by this issue will help them decide whether they need to push for a solution faster.

    So, to all that are experiencing this issue; please respond to this post

    Thanks!


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Wednesday, June 26, 2019 9:18 AM
    Moderator
  • Thanks for all the information on this issue. I encountered this issue while building WEC7 image on Windows 10 OS build 17763.557. I had no issues building WEC7 images prior to June 26. I looked at the update history on my computer, I saw KB4495590 and KB4465065 Windows Update installed on June 26, but did not see all the other KBs mentioned earlier in the post. As Eugene pointed out, it does seem that combination of Windows build and KB update are causing issues.

    Based on a suggestion for a possible workaround from a post, I tried launching Microsoft Visual Studio 2008 from an Administrator Command Window and tried building the image and it worked for me.

    Thanks!

    Sunday, July 7, 2019 2:35 PM
  • I have the same problem.

    Using the command windows workaround. 

    One thing I have found was that I have to open the solution from inside VS. If I have it in the command line the workaround does not work.

    Jakob

    Wednesday, July 10, 2019 5:07 AM
  • I'm using Win10 1809 17763.615 and having the same problem, but unlike others there are no updates for me to remove.  Running devenv as Administrator does not help, nor does setting compatibility mode on pbspawn.exe.

    Tuesday, August 6, 2019 6:41 PM
  • Try running "wusa /uninstall /kb:4493509" from an admin cmd.

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, August 6, 2019 6:43 PM
    Moderator