Yes it works, but it’s a risky unsupported fix and could render a server unbootable if done improperly 
Doing a product upgrade might also fail later on because of the changes and leave the server in a worse state. Thats the reason I chose not to do it on my server. So do take care and have a good alternate backup and recovery plan if this is a critical server.
The developers have identified the cause of the issue in the installer configuration and should be releasing a corrected installer as part of our next major update patch, or the major update patch after next. You shouldn't experience this issue again for this system unless you re-install the AV. Please let me know if these registry entries revert back to the broken path again.
I got this, it looks like allmost the same as you get) Lets see, what happens next version.
Does anyone know what is going on with this?
I havent had any update from Avast support for 3 weeks.
The way its going I will end up moving Anti-Virus software.
I just tried 17.7.2526 today; same problem on my test VM. Can anyone else confirm?
Very disappointing that a company with data security as it’s core will consciously allow this problem to continue 6 months later. System State is an OS core feature, also with the aim of data security. It’s not like it’s a 3rd party backup Avast can blame.
I too will be shopping around for another vendor, but first I might post something and see what happens in the https://forum.avast.com/index.php?board=15.0 Beta board since the cloud beta board is dead.
Please follow topic https://forum.avast.com/index.php?topic=210048.0
Looks like the target for the fix is 17.8
Exciting! ;D
Perfect. I will wait for that version.
Thank you.
Maxi
Its look the new version 7.8 has sorted the issue.
Yes I can confirm my Test VM is able to complete a System State backup now with Avast v17.8
Looking forward to finally installing to my Production host!
Perfect. Glad to hear it!
Unfortunately I have to post again in this thread. Our same reseller who discovered the bug months ago, informs us that since days ago he has observed that the problem is happening again in one of his customers.
This customer had the problem before, then it was fixed when it was announced here that it had been solved, and now it seems to happen again.
Have any of you noticed that the problem is happening again? Thanks for your information.
I am still running 17.8 and still working fine.
I assume you have 17.9. I refuse to let program autoupdates run on my network for reasons like this.
I suggest you set a policy to turn off program updates and add the server to it, then downgrade to 17.8 and see if the issue goes away. If not, you might have different issues (particularly if it’s just one customer).
Thanks for the heads-up. I’ll definitely test before I upgrade and report back if I have anything to report.
If you are convinced 17.9 regresses, please report the issue to support, as will I!
Hi, first of all, thank you very much for your reply.
The new bug (or the same repeated) was reported by one of our resellers (we are Avast Distributor), is not from a direct customer. We have asked this reseller again and he inform to us that the problem is happening now in 2 of his customers, both with Windows Server 2012. Because of this, and because he was one of the first persons to report this bug months ago, we give value to his words and we believe that it is possible that in some of the latest AfB versions there is a bug (again) with the backup of Windows Server.
Thank you for your tips, we will take them into account. And please, if you do some test with the latest version of AfB, I would appreciate it if you could tell us the result here.
I installed 17.9 to a test server and no problem. It was a fresh install and not an upgrade from 17.8 but previously it made no difference anyway.
It sounds like the customers are having different problems unrelated to this old bug, but uninstalling Avast could help prove or disprove it as being a cause.
Check the event logs for clues and the Windows Backup logs, as it might be failing but with a slightly different error. Make sure Windows Backup still works without system state to narrow down the problem. PM me if you need some help.
I’ll eventually upgrade my production server and if I have a problem I’ll be sure to let you know.
Good luck
Hi friend, thank you very much for your valuable information, it’s very useful!
We will be in contact here if there are more to say about this.
Once again, thank you for your time and help.
system: Windows Server 2008 R2
Avast console on premise: 7.29.911
There is an error while trying to use Windows System State Backup:
wbadmin start systemstatebackup -backuptarget:f:
this command returns an error:
Error in backup of C:\program files\avast software\management console\console\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.
I guest the problem is in doubled "", but how to fix this?