I tried cloning a Windows 11 computer (exact H/W model), no apps installed (including Avast). The image it came from works fine. The cloned system will not enable antivirus modules, it does report into the portal, I could even trigger an install of various modules from the portal (one attempt was I installed PRC only, then added the install for AV, Etc.).
I can only enable the basic AV module, all others indicate they are disabled by the admin (Web shield, Etc.). If I move the system to a “all disabled” policy, the end system does disable the AV module. Moving back to an “enabled” policy does NOT enable any AV modules.
Is cloning just a bad idea? Or is there a way to reset the machine ID somehow? All other installed apps and such appear to be working okay. I was just trying to save time as I have a number of like systems to deploy. But not enough to do the old-school sysprep (if that’s even a thing any longer).
I’ve tried the available CTRL+ menu options in the Avast tray icon, no joy.
1 Like
Per chance does or did the original machine have Avast installed? I’m wondering if there are some artifacts/remnants of the Avast program that got cloned over. If yes, I would run the Avast cleanup tool, make sure the device is deleted in CloudCare, and try again.
Neither system ever had Avast installed prior to cloning.
On the cloned target, I uninstalled via the standard methods, and after encountering this trouble, ran a fresh download of the cleanup tool (ran in safe mode). Still no joy.
I’m going to revert the problem system to factory delivered (image backup was done before 1st boot just in case of shenanigans like this) and that should make things all happy.
Thanks for your reply!
TYSM AplusComputers for posting that link.
I don’t think it pertains to me in this case, as neither system has ever had Avast installed prior to cloning. I do see that it’s referencing MAC addresses, which should be unique between source & clones.
I tried the step “Repairing Clones Created Without Invoking ‘setup.exe -c’“, and get only a terse “Missing Parameters” small window. I don’t know what it’s trying to indicate by 64-bit / 32-bit registry keys in that step.
I did add the CL registry key and set its value to 2 as cited in the article, and installed Avast anew. It added a 2nd system in the portal with the same name, both remained listed offline. On the system, Avast items were in the Start menu but only “Avast Business Web”. Surprisingly, uninstalling from the portal did trigger an endpoint uninstall, leaving behind an AvWrapper.exe task running. Too squirrelly for me, I’m done experimenting.
I am going to reimage from factory or just install Win 11 from scratch. Not worth any further fumbling around.
2 Likes
There is a procedure for cloning a Windows 11 machine that is a bit different. You cannot allow the first machine to finish and create it’s GUID. It must be a “Generic” image with no user created.
After installing Windows, do this:
When booting for the first time, stop at first screen and press “CTRL/SHIFT/F3” to enter “Audit” mode. Do not fill in anything, just let it continue as administrator.
Install updates and any standard software. DO NOT run Edge. You may need to turn off Bitlocker.
After installing updates:
Run c:\windows\system32\sysprep\sysprep with OOBE and “generalize” after all updates and software is complete.
Shutdown unit when Sysprep is done.
Create your image file and use it to clone to other computers.
I have used this procedure many times for the past year, and it seems to work each time. It normally will work on different hardware as well, most of the time.
I hope you find this helpful.
Have a great weekend.
Dave
1 Like