NOTE: You can enable the listing of Hard Drives under 'advanced drive properties' If this device is not a Hard Drive, please e-mail the author of this application Using 'autorun.inf' label for drive E: 'Ventoy-SSD'ĭevice eliminated because it was detected as a Hard Drive (score 21 > 0) The DeleteFileU() call is failing for your specific temp directory, for whatever reason.Īll in all, since none of 1-3 are really viable as explanations, I'm starting to lean towards the explanation that you might have your temp directory using an uncommon path, and that this may be causing an issue with DeleteFileU(), because that's the only remotely logical way that can explain your issue when nobody else is seeing it.Ĭan you provide the full path of your temp dir?.But if that is the case, then you will see a line Using external loc file 'xyz.loc' in the Rufus log, which you don't see. If the external_loc_file boolean variable was somehow set to TRUE.If the temp loc filename variable was somehow zeroed during execution (very unlikely, as you'd experience other issues then).If Rufus crashes on exit before it reaches the deletion call. Therefore the only circumstances where Rufus may not delete the temp loc file is: Chances are it's a text file and if you can copy/paste the beginning of the file, it can give us some clue.Īnd again, I am not seeing it, and this is not an issue I have ever seen on any of the PCs I tested.įor reference, we do have an explicit call to delete the loc file on exit in the code per, so it's not like we somehow "forgot" to delete the file in the source. So, again, this does not appear to be the universal easy-to-replicate issue that you assume it is, and there is some component of your specific environment that is at play here.įor one thing, can you take a look at the tmp file left behind and tell us what it contains. Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.įound 517 officially revoked UEFI bootloaders from embedded listįound 2351 additional revoked UEFI bootloaders from this system's SKUSiPolicy.p7bįound USB device 'Mushkin Ventura Ultra USB Device' (174C:55AA) ĭisk type: FIXED, Disk size: 120 Гб, Sector size: 512 bytesĬylinders: 14593, Tracks per cylinder: 255, Sectors per track: 63 SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E This means that some controls may still be displayed using the system locale. NOTE: No Windows Language Pack is installed for Ukrainian (Українська) on this system. Thank you very much for your time playing with this.Windows version: Windows 11 Pro for Workstations 圆4 (Build 22621.2070) I cannot solve this alone, since it doesn't fail on my computer. I don't think that those are needed, but you can test. bios/com32/libcom/libcom.c32, and maybe some others from the. However, it is possible that some more files need to be added, so if only vesamenu.c32 won't help to fix your problem, try to copy also. If this helps to resolve your problem, please reply here that vesamenu.c32 is the only file which needs update. bios/com32/menu/vesamenu.c32Ĥ) copy the vesamenu.c32 to your USB disk with Slax and try to boot Slax again. So, if you are experiencing these troubles, please try the following and let me know what helps:ģ) find file. Several people reported they have problem booting Slax from USB device, with the following error message displayed:įailed to load com32 file /slax/boot/vesamenu.c32I am not able to replicate this error, so I need your help to find out what particular change fixes it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |