We ran into a similar issue with our old 1607 machines and if I remember right, the problem was introduced by a patch. I want to say it was the March or April rollup. One of my co-workers came up with a workaround by tossing the image into the cache or something with SCCM. Thankfully, the problem isn't there in 1803.