Well, thing is... we don't know why it happens. The logs in your support package indeed show that the file couldn't be restored - but the error code implies the file simply wasn't found, and it's not clear why (since the transfer to quarantine seems to have succeeded without any problems, according to the logs).
It's also not clear if the issue has actually any connection to the dual-boot scenario... or if it's something specific to the particular OS, without any connection to the other OS.
So, let me ask for some details that may help us reproduce the environment...
- You've got two Windows OSes, right?
- If so, do you have Avast installed in both of them? Or you've got Avast in one and AVG in the other... or the other is without an AV?
- What access rights does the C:\Temp folder have?
- The video shows that you have both Avast and AVG installed in the first OS. Was is always the case (i.e. could that fact be the cause of the problem), or did you install AVG only after you found out you couldn't restore the file?
Correct both are Win10 Pro 22H2 Build 19045.4412, All updates that come down the pipe are installed.
No, I have ESET ESSP 17.1.11.0 on Disk 1 Samsung SSD 850 EVO and then have Avast on Disk 4 Samsung 870 QVO, AVG did not cause the issue as the issue was present prior to it's install. I just installed AVG alongside Avast to show it worked perfectly fine in this scenario. I then uninstalled Avast and left AVG and AVG still continued to work flawlessly.
I also then created that video to show Avast that the same version of AVG does not have the same issue as Avast.
As far as permissions I have full control and I can create and read and write to any file in that folder as well as Eset is able to restore to that folder as well as AVG is able to. The only program unable to restore to that folder is Avast.
From my view Avast has the issue but AVG does not yet they are both the same versions, So what is different between the two that would cause the issue with Avast?
The issue does not present itself unless a drive letter is assigned to the non booted os drive. I can mount it as a volume in a folder and no issue. I can mount the non booted os to a folder and then assign a drive letter to that folder and it works correctly.
So it seems Avast has a issue when you have a os on two separate drives both with drive letters assigned, Maybe a hook causing the issue?