Working with some Windows 10 2016 LTSB PCs running Lab robots last week, I noticed they didn’t have updates showing as applicable even though they were in collections with ADR based update groups deployed. We have an LTSB 2015 test machine in our area, so I checked his, same story. I double checked, and we do have the product Windows 10 LTSB enabled, and in that ADR, we are including updates for that product.

To keep the Update Package size down, I had previously had filters in our ADR to not include updates for old Windows 10 builds, as our plan was to require reimages of these initial few Windows 10 images anyway (-1507, -1603, -1607, etc.).

I removed the filters from that ADR last week and manually re-ran it. Checking today, these LTSB PCs have received updates now, labeled for the versions I had filtered out.

The following is from our test machine, which is running Windows 10 LTSB 2015, but receives updates for Windows 10 1507 (I’m assuming that’s the build the 2015 LTSB is based on.

After looking at both 2015 and 2016 LTSBs, it appears the following is true:

• 2015 LTSB Uses for Updates Windows 10 1507
• 2016 LTSB Uses for Updates Windows 10 1607

Something to keep in mind if you have LTSB in your environment: Even though it will add to update package sizes, updates for older current branch builds are still needed if you have any LTSBs floating around!