Hey all,

I hadn't noticed this sooner but since the agent in a Windows 7 machine of mine had been automatically upgraded from v8.0.7327 to v8.1.7551 back in June this year, there have been no Site Manager scheduled backups taking place at all.
When I try to manually start the Agent service within the Windows Services console, it immediately stops. Likewise if I attempt to run it from the command line with the -d (debug) switch.

Looking in the C:\ProgramData\Macrium\SiteManager\agent.log file, all it has in it is the following, which is exactly the same as what I see when I try running it from the command line, as mentioned above:


I have tried reinstalling the agent manually (as in downloading 8.1.7633 from my Site Manager server, copying it across to the Windows 7 machine and then installing it that way) but the outcome is exactly the same.

Has Windows 7 support for the Agent been discontinued? If so, where can I download the last v8.0.x agent to restore functionality?

I should also note that my Windows 10 machines have no problem from any and all automatic agent upgrades (currently running v8.1.7633), which is why I raise the question about Windows 7 compatibility/support.

+x

 

Alex - 11 September 2023 8:45 AM

Windows 7 is fully supported - the issue here is that for some reason, your Windows 7 machines have a registry key set that indicates they're still installing Windows / failed installing

On service start, we check the registry key below to see if Windows install is running (it's possible to use SysPrep to deploy a system image with the Macrium Agent already instaled) and exit if it is, so that we don't interfere with the install / sysprep process.

Can you check the registry key below?

Many thanks for the prompt (relieving) reply and apologies for my delayed response in kind.
That's exactly the situation, though I can't understand why a four year old installation had suddenly gone into that state a few months ago. Perhaps a Windows Update gone wrong? Certainly nothing running on the system that I would expect a Sysprep to be executed, and no system errors flagged in the Event Viewer nor chkdsk.
In any case, I've gone cowboy and manually edited both the registry entry and the state.ini file to read IMAGE_STATE_COMPLETE, which has made the Agent happy again.
Once again, many thanks for your help!