![]() The update history of this system goes back to or so and no CU can be found. It is getting security updates for only Office 2013. Now the system that has a build number ofġ4393.0 as far as I can tell has never received a CU. I am sure that is the incorrect term, but it seems to increment when cumulative updates are applied. You may notice that each system has a discrepancy on what I call the "minor" release info. Take a look at the following screenshots collected from two of our LTSB We have deployed Windows 10 LTSB Version: 1607 Build:14393 on quite a few systems and I have started to notice a strange pattern. ![]() Hello everyone, I have a strange one here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |