Possible regression on the failure to create autorun.inf notice

[pbatard]

A user reported the following:

I think that the latest Rufus (Rufus x86 v3.9.1624) may have an issue,
or at least not deal as gracefully with an error as previous versions,
which stops it working.

On our PCs creation of an “autorun.inf” file is blocked entirely.

The relevant parts from the log seems to be below:

From 3.8:

Extracting files...
Image is an ISO9660 image
This image will be extracted using Rock Ridge extensions (if present)
Extracting: D:\autorun.inf (146 bytes)
Unable to create file: [0x00000005] Access is denied.
   NOTE: This is usually caused by a poorly designed security solution. 
See https://goo.gl/QTobxX.
   This file will be skipped for now, but you should really look into 
using a *SMARTER* antivirus solution.
Extracting: D:\boot\grub\efi.img (304 KB)
Extracting: D:\boot\grub\font.pf2 (4.9 KB)
Extracting: D:\boot\grub\grub.cfg (2.3 KB)
...

Whereas from 3.9:

Extracting files...
Image is an ISO9660 image
This image will be extracted using Rock Ridge extensions (if present)
Extracting: D:\autorun.inf (146 bytes)
Warning: Could not read file pointer [0x00000006] The handle is invalid.
Write error [0x00000006] The handle is invalid.
   Error writing file: [0x00000006] The handle is invalid.

I’m aware that this problem is caused by our IT dept. antivirus
solution, but there is no changing that, and (apart from the autorun.inf
file!) it all worked on previous versions.

I’m assuming something changed in the way 3.9 writes the files – is it
possible it could recover in the same way that 3.8 did, or are we stuck
with 3.8 forever more?

[pbatard]

I believe this was introduced in 4c5adf0 since we are no longer receiving an error code from CreateFile[U]() but from NtCreateFile(), which returns an NtStatus that is then converted to a conventional Windows error code.

Most likely, the ERROR_ACCESS_DENIED code we were getting previously has shifted to an ERROR_INVALID_HANDLE code.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.