I am trying to generate a windows 10 image by sysprep, I install the sophos antivirus with the respective step by step to generate the golden image and after this I run the sysprep and the image is damaged, you could tell me that I should take into account in order to have the sophos antivirus installed inside the image it is for azure virtualized desktops
Hi David Lopez2,
Thank you for reaching us, what error are you getting upon loading your image? Aside from Sophos being installed on your Sysprep system was there any other application installed on your…
Thank you for reaching us, what error are you getting upon loading your image? Aside from Sophos being installed on your Sysprep system was there any other application installed on your Image?
Also, ensure you're following every section of this KB article https://support.sophos.com/support/s/article/KB-000035040?language=en_US to make sure you're deleting the files required.
Good morning, the test was made to create the image with all the required applications and without the sophos antivirus and it works without problems, but when we make the image with the sophos antivirus, follow the step by step of the golden image, the image is damaged
good morning, yes sir have been done in the 2 ways create the golden image manually or with the script and the result for the image is the same is damaged
Good morning, if you could help me with my concern, I would appreciate it very much
To further investigate this one, I would suggest you please raise a support case for this issue. please share with us the case ID once created and will proceed on checking this with our internal team.
hi we have the same problem, sysprep hangs with error
We are also having the same issue. We have run the golden image script and once running sysprep we are unable to boot into windows again. We get the same error message as shown above.
below is the event log which shows Sophos causing this issue. I have prepared the same image without Sophos and it works ok.
Any help would be appreciated.
We have raised this one to our internal team, and to further investigate this issue, can you please create a case ID and collect SDU logs to further investigate this matter