Forum Discussion
Issues/Problems with Release 17733
First, thanks for fixing the Windows Deployment Server problem. Now for the still remaining problems.
1. As with previous 2019 releases, with IPv4 disabled, and only using IPv6, when trying to reach other Windows machines by single name, LLMNR fails - it worked fine with Server 2019.
2. Docker images such as the Web Server that we used with Server 2016, will not work with Server 2019 with message that Server version is incorrect. - it seems that there are only special Docker images for Server 2019, but we can't find one that works.
3. When trying to restore an image with DISM, a message comes up that the Data is incorrect/corrupted and the restore halts. This happened even though the creation of the image work perfectly with DISM. The "Check Integrity" switch makes no difference. (Note with version 17733 we have some more testing to do with this 3rd problem however).
11 Replies
- Brentfor
Microsoft
Thanks for the feedback, Bill! Please provide more context on #3 when you have it. We are not sure what your scenario is here that you are attempting.- Bill ReichertCopper Contributor
We have created an image from a fresh install saving to an external hard drive, cleaned and reformatted the original drive, and are trying to apply the image using the command:
dism /apply-image /imagefile:F:\Images\fresh.wim /index:1 /applydir:C:\ /checkintegrity
Upon running the command we get:
Error: 13
Data Invalid
We have tried this several times with multiple builds of 2019.
- Sudhagar Thirumoolan
Microsoft
Hello Bill,
Thanks for reporting this. Could you please share additional steps \ command lines on how you captured the image?
Could you also please share the dism log from c:\windows\logs\dism folder?