This can be indeed related to the environment change, specifically August 1st images update. Please try to set image to the Previous Visual Studio 2017 and see if this helps.
But please come back to us in any case. Even if switching to "previous" helps, it can be treated only as a temporary workaround, valid only till next update. So we will be needed to root cause it together.