Windows 11 Enterprise IoT LTSC 2024 Issue

Question

Windows 11 Enterprise IoT LTSC 2024 Issue

Luca Orbi 20

Hello,

Our company uses Windows 11 IoT LTSC 2024, and we're having a problem. Our embedded devices can connect to the LAN to communicate with other devices. The problem is that when I try to connect the devices to the LAN, they crash. I checked the packets with Wireshark and discovered that they're exchanging packets with another IP address, namely Akamai Technologies. I think it's trying to update something, but I need to block it.

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Jason Nguyen Tran 12,475 Independent Advisor

Hi Luca Orbi,

Based on your description, the traffic you observed to Akamai Technologies is expected behavior, Windows Update and certain Microsoft services use Akamai’s content delivery network (CDN) to distribute updates and telemetry securely. This is not unusual, but in constrained IoT environments it can sometimes cause instability if the devices are not permitted to reach those endpoints.

To prevent crashes, I recommend first ensuring that the devices have the latest cumulative updates applied, as stability fixes are regularly included in LTSC releases. If you need to block external update traffic, you can configure Group Policy or Mobile Device Management (MDM) to disable automatic updates, or use Windows Update for Business policies to control when and how updates are delivered. Another option is to redirect update traffic through a local WSUS (Windows Server Update Services) or Configuration Manager deployment, which allows you to manage updates internally without devices reaching out to Akamai.

If you choose to block outbound traffic, please be aware that doing so may prevent the devices from receiving important security patches. For IoT scenarios, the recommended approach is to use WSUS or a controlled update channel rather than outright blocking. You may also want to review firewall rules to ensure only approved endpoints are accessible.

I hope this explanation clarifies and provides options to stabilize your devices. If you find this answer helpful, please consider clicking Accept Answer so I know your concern has been resolved.

Jason.

Luca Orbi 20 Reputation points

2026-02-08T21:05:58.6633333+00:00

Hello,

The device should be a "closed box," meaning it shouldn't receive updates or update itself. We'll do so every six months or even annually. So, the solution you recommend is to block outgoing traffic? If I go this way, TeamViewer might have problems. I need to adjust the firewall rules for that, right?
Jason Nguyen Tran 12,475 Reputation points Independent Advisor

2026-02-09T07:08:44.14+00:00

In this scenario, the most effective approach is indeed to block outgoing update traffic, while still allowing the specific applications and services you rely on (such as TeamViewer) to function.

To achieve this, you can configure your firewall rules to deny outbound connections to Microsoft update endpoints (which often resolve through Akamai), while creating explicit allow rules for trusted applications. For example, TeamViewer requires access to its own set of servers, so you should whitelist those domains or IP ranges to ensure remote management continues to work. This way, you maintain control over updates while preserving essential connectivity.

It’s important to document and regularly review these firewall rules, especially if you plan to manually update the devices every six or twelve months. When you perform updates, you can temporarily lift the restrictions to allow the devices to reach Microsoft’s update servers, then reapply the block once patching is complete. This ensures your devices remain secure and stable without unexpected update activity.

Answer 2

Jason Nguyen Tran 12,475 Independent Advisor

Hi Luca Orbi,I’m just following up to see if the issue has been resolved. Let me know if you need any additional information.

If this answer was helpful, I’d really appreciate it if you could click Accept Answer. 😊

Share via

Windows 11 Enterprise IoT LTSC 2024 Issue

1 additional answer

Your answer