Hi @kana612,
One additional thing I’d check here is the Windows user context, because the difference between Attended and Unattended execution is a very important clue.
You are resolving the Downloads folder through:
Registry.CurrentUser
That means DownloadPathValue can be different depending on which Windows account/profile is running the Robot.
So I would log these values during both Attended and Unattended execution:
Environment.UserName
DownloadPathValue
and also:
String.Join(vbCrLf, System.IO.Directory.GetFiles(DownloadPathValue))
Then check whether the expected standard...WEEKLY...zip file is actually present in the exact folder used by the Unattended Robot.
I would also temporarily avoid FileList(0) and check the count first:
If FileList Is Nothing OrElse FileList.Length = 0 Then
Throw New Exception("Expected download was not found. Folder: " & DownloadPathValue)
End If
Then use FileList(0) only after confirming that the array contains an item.
There is another thing worth checking in the wildcard itself. Make sure it exactly matches the downloaded filename, including dots. For example, if the real file is:
abc_standard20260908WEEKLY.xlsx.zip
then the pattern needs to match that exact structure.
Given that Attended works but Unattended fails, I’d investigate the Windows user/profile + resolved Downloads path first, before assuming the download itself is failing.
That would also explain why visually checking the download in the browser shows the file successfully downloaded while Directory.GetFiles() in the Unattended execution still returns an empty array.