Impact of Windows Embedded Compact 2013 End of Life on Computer-on-Module Boards

Elsanan, Amr 0 Reputation points
2025-01-30T13:16:06.5066667+00:00

With the announcement that Windows Embedded Compact 2013 will end its license by the end of May 2028, what will be the implications for computer-on-module boards, specifically those using the IMX 6 processor, after that date? Does anyone know?

Windows for IoT
Windows for IoT
A family of Microsoft operating systems designed for use in Internet of Things (IoT) devices.
409 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Daisy Zhou 28,906 Reputation points Microsoft Vendor
    2025-01-30T13:56:30.48+00:00

    Hello Elsanan, Amr,

    Thank you for posting in Q&A forum.

    The end of licensing for Windows Embedded Compact 2013 will have several implications for computer-on-module (COM) boards, including those using the i.MX 6 processor. Here are some key points to consider:

    1. End of Support:

    With the end of licensing, Microsoft will also likely stop providing updates, security patches, and technical support for Windows Embedded Compact 2013. This means systems running this OS will be more vulnerable to security risks and compliance issues.

    1. Security and Compliance:

    Without regular security updates, systems running Windows Embedded Compact 2013 will become increasingly susceptible to malware and other cyber threats. Organizations in regulated industries may face compliance challenges as they are required to maintain up-to-date security standards.

    1. Software and Hardware Compatibility:

    Over time, newer software and hardware may not be compatible with Windows Embedded Compact 2013. This could limit the ability to integrate new technologies or peripherals into systems using the i.MX 6 processor and Windows Embedded Compact 2013.

    1. Technical Debt:

    Continuing to run on an unsupported operating system can accumulate technical debt, making future migration efforts more complicated and costly. Organizations might face higher maintenance costs and potential downtime due to the lack of support.

    1. Migration to New Platforms:

    Organizations will need to plan and execute a migration strategy to move to a supported platform. This could involve:

    Upgrading to a Newer OS: Moving to a more recent version of Windows Embedded or transitioning to a different embedded OS.

    Software Redevelopment: Redeveloping or porting applications to be compatible with the new operating system.

    Hardware Updates: Evaluating whether existing hardware (like the i.MX 6 processor) is compatible with the new OS or if a hardware upgrade is necessary.

    1. Vendor Support:

    Some hardware vendors might offer extended support or migration assistance for their products running Windows Embedded Compact 2013. It’s wise to check with the vendor of the i.MX 6-based COM boards to see if they offer any migration tools, services, or support extensions.

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  2. Sean Liming 4,601 Reputation points
    2025-01-30T17:37:36.59+00:00

    To follow up on Daisy's response:

    If the system is not connected to the Internet, all the security concerns are a little less important. Even if the system is functional, having an OS without support is something to consider. Bottom line, you should be planning to move to a different OS and/or COM module, now.

    I have several clients who are running into WEC EOL, and it is best to find the alternative before the EOL date. Windows IoT Enterprise LTSC might be a candidate, but keep in mind migrating WEC apps is not strait forward. Windows IoT Enterprise LTSC ARM supports i.MX 8, but it is slow.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.