[0x00000057] Error While Formating - Only on Windows 11 #1779
Comments
|
Thanks for the report. This is a problem with the Windows Store version of Rufus running on Windows 11, and the source of the issue. It looks like, starting with Windows 11, Microsoft rescinded some permissions that they used to provide Windows Store apps, including the ability to access the VDS service or the ability to call on the Windows formatting APIs. In other words, Windows 11 restricts the ability of store installed applications like Rufus to perform system operations like formatting a drive. If you are running Windows 11, you should use the non-Store version of Rufus, which you can download from the official site as you will find that it works much better (since Microsoft has not yet applied the same restrictions to non-store applications): No wonder Microsoft calls Windows 11 more secure than Windows 10, when they have restricted things so much that advanced applications can no longer accomplish legitimate tasks... I'll see if I can log a ticket with Microsoft's Windows Store support, but I get the feeling that they're just going to say that the new security restrictions are here to stay and that Windows Store apps should limit themselves to simply doing things in their little corner and not try to format a drive... |
|
Hi there, Thanks for the quick response. I've tried the standalone version, and although the error code switches to 0x00000005, it's not working either. I've read the FAQ, and I have Windows Defender fully disabled from regedit, so there's no Manage Controlled folder access running. Here's the capture and the log:
Log |
|
UPDATE: I've read the FAQ further and, it seems that cheat mode "ALT+ , " on BOTH standalone and Windows Store versions, fixes the problem, here's the log of a succesfull formatting. Log |
|
Interestingly, I am no longer able to replicate the issue on my test Windows 11 machine, using the Windows Store version (be it with or without exclusive drive locking, i.e. Alt-, enabled or disabled). The only thing that happened since my last test is that I installed the 22454 → 22458 build update and rebooted. But, considering that you were already running 22458, we can rule out the update for this change of behaviour. Did you reboot your machine since you installed the Rufus Windows Store app? I have a feeling that the store version may fail until a reboot has occurred or something... I also have not seen the I'm going to test some more, because it's very puzzling that, after update and reboot, the Windows Store version suddenly started to work for me whereas I did not change anything on the system. And of course, I'm going to play with drives that contain MSR's to see what happens... |
|
Hi there, I've rebooted to test this out, but I cannot format without using the Alt-, hotkey. In my case, it does not matter if I'm formatting from MBR to GPT or else. It won't work either way. Here's log after rebooting (failed formatting): And here's log using Alt-, cheat mode on the same settings and disk (formatted correctly): |
|
Well, I tested on a different Windows 11 machine (this time not a Windows To Go one, but a system that went through a full install) and, as long as the USB I was trying to format didn't have an MSR, I saw no issue using the Windows Store version (apart from the notice about not being able to access I did see So my current conclusion is that this looks mostly like Windows being an ass about preventing access to system partitions (which isn't exactly new), and not a systemic issue that everyone will face the minute they try to format a drive using Rufus on Windows 11. I'll see if I can add new workarounds against this annoyance, but I think I'll wait until the formal release of Windows 11 to see how many folks are actually impacted... |
|
I've tried on different system too, and both Alt-z and Alt-, work. I'll keep using Alt-, since zeroing the drive takes long, even using the fast mode.It's very weird. By the way, I forgot to congratulate you for the amazing work you've been doing. This tool is a MUST. Thank you. |
|
I'm on Windows 11 dev 22463.1000 and I'm seeing the same behavior, Alt+, fixes it. |
|
Thanks for the report. Considering that I am still not able to replicate it, I am curious to know what edition of Windows 11 you guys have installed. Was it Home? Pro? Enterprise? Something else? I'm thinking that the edition may also be a factor in this, especially if you you are running Windows 11 Home edition, as Microsoft seems to restrict things a bit more on Home... |
|
In my case, Windows 11 Pro, right now build 22463.1000 from Dev Channel. |
|
@xatornet, can you confirm that you are only seeing the error when the USB you are trying to reformat contains an MSR? Or do you also see it when there's only a single regular data partition? |
|
I've also experienced this issue, previously on 2200.12x, then after cleanly installing again to the DEV build, I'm on 22458 and cannot upgrade t o22463, nor was I able to make the installer drive via Rufus. The info here helps a lot, and I'm going to try to both diskpart clean as well as quick format the drive and see if this works to create the installer from 22463 .ISO. I will report back if the error persists or not, and during which of those conditions. Windows 11 Pro 22458.100 |
|
@JohnLGalt, can you please provide a full log from Rufus of your error? This will help me devise the type of workaround I should apply in the next version of Rufus. |
|
Sure thing! Except I'm not sure how to obtain said logs from portable version. As soon as I figure that out, I'll grab one without modifying the current USB, and attempt to use Rufus so it grabs full logs. Found the log area - trying now, will save and post. |
|
Click the small log button (left of |
|
@pbatard Log when trying to use Rufus on UUP Dump created .ISO for Win11 build 22463: |
|
Can you please not truncate the log? I'm afraid I need to see the whole thing. Thanks. |
|
From start to finish you mean? I think I cleared it before running, I assume that is what you mean? I'll clear it now, then close Rufus, then open it again and try again and repost with full log, sorry about that. |
|
|
Thanks a lot. That's what I wanted to see. |
|
I am unable to format a usb on the latest and previous dev builds but not on beta builds |
|
I can confirm this issue. However i can't get it to format if i hit Alt+ either. Running Rufus 3.15 and latest Windows 11 Pro Dev build. |
Sorry for the late response. The issue is very weird and here's why: I've tried formating a GPT pendrive to GPT again, to rule out the issue and check if it happens not only on MBR to GPT formatting. And it correctly and succesfully did it, as it is showed on the log: But here's the catch. I've connected another disk, a bigger one (I had to enable "Show USB hard Disks option" for Rufus to show it listed), and tried it again to format from GPT to GPT, and then it failed: So I think that the issue has more to do with the kind of drive we use, more than if it's MBR or GPT. But I'm no expert on this :-) |
It's Alt+, or Alt plus comma. It should say at the bottom something like this:
|
Ah ok, i'll try that, thanks |
|
It gets a little weirder, format fails in dev build but is fine on beta builds. So flashed an iso in beta and then went back to dev. It worked fine when overwriting a previous successful flash so I wiped and formatted with diskpart and tried again in the dev build......again no go, format error. So summary:
|
|
For the record, I installed the latest dev build ( And, similarly, that's also why disable exclusive drive locking works too, because then we are simply telling Windows "You wanna keep a lock on these partitions even though we're going to delete them? Fine..." I am however not seeing What I am seeing on the other hand are As such I am planning to add the following workarounds:
I believe the above should be enough to get us going on Windows 11, especially as it looks to me like some of the other issues being mentioned in this thread are probably not directly related to using Windows 11... I'll try to produce an ALPHA with these proposed changes when I have a chance, so that you guys can test and report (unfortunately, I can't produce a Windows Store ALPHA, so Windows Store testing will have to wait for the actual 3.16 release). I'll keep you posted. |
Just so you know, though, I'm trying to build a USB installer of 22463.100 from .ISO while running 22458.100 Dev build, and I'm only using the portable version. The whole point was to build the USB installer because 22463.100 will not install via Windows Update, so I had to use UUP Dump to generate an .ISO for 22463.100 and put it on USB to try an in-place upgrade from 22458.100 --> 22463.100. I'll give all the manual workarounds one more shot, and if they still do not work (and I watch for your pre-release builds always, too, so if that drops soon I'll try it as well), and hopefully I can get this resolved. I had an issue moving from Beta preview release to DEV 22454.100 release, and just cleanly installed Windows not a month ago, and simply don't have time to cleanly install again, and with WU not taking the upgrade, it's either 1) in-place upgrade, or 2) wait for next release and just skip 22463 entirely. |
|
@adiantek, does Alt-V or Alt-, work? |
Yes, I need to alt-v or alt-, or both and it works. Thanks |
By the way, you will probably want to restore rufus update functionality in the windows 11 store as this can be done by the developer: |
I don't think I want to do that. For one thing, my understanding is that it's very difficult to write to the location where the store executable is located, and I'd need to overwrite the running executable that is always called Considering that I am always publishing a new Store version for new releases now, and that the Store application update mechanism can take care of updating the Store version of Rufus, it would be kind of counter productive to have to reinvent the wheel, when Store updates should work just fine. |
|
The new Rufus 3.16 BETA (available here) should work better with Windows 11. Please test it and let me know if you are still seeing issues. |
|
NB, I had to re-upload the BETA, since I had leftover code in there that shouldn't have been present. If you are testing on Windows 11, please make sure your BETA says |
|
I can confirm. On Windows 11, 3.16 beta now works (I was having the same error as OP). |
I can also confirm that it works on the latest Windows 11 dev build. Amazing work :-) EDIT: I spoke too soon. This fixes the issue for me sometimes. I've been able to format correctly some disks, but some others still give the 0x00000057 Error and have to resort to cheat codes. |
|
beta fix it for but after closing explorer.exe because its said the disk is being used by it once i closed that window ''This PC'' and tried again , its worked |
|
I'm about to use the 3.16 Beta to make a USB drive of the official Windows 11 from .ISO while running DEV build 22468. I'm betting I have no issues, and will report back shortly. |
|
I had 0 issues using the initial BETA for make a UFD of official Windows 11 .ISO downloaded directly form Microsoft. At the time I was on Insider Preview DEV build 22468, my system having jumped from 22458 (leapfrogging 22463). I see a new Beta is out, I am I correct in assuming that nothing new has been done though on Win 11 support since the first Beta (this was the only issue linked on the changelog, hence my assumption)? Anyhoo, now that I've installed the final release version of Win11, I'll be making a few more tests of the latest DEV builds for installing on other devices. I'll report back if I encounter any more issues with Windows 11 in any way. |
That is correct. I am now in a wait and see approach regarding the running of Rufus on Windows 11, until the 3.17 release (i.e. the next release after this one). The new BETA is the result of wanting to allow users to have the option to create Windows 11 installation media that doesn't require TPM 2.0/Secure Boot/8GB+ RAM for installation. |
|
Awesome news. Since I have the regular install, I'll be throwing the various Insider builds builds into VMs, but I have a couple of physical machines that I plan to continue to test on, so I'll be watching for any more issues - I suspect, though, that I won't find any, now that I'm not actively running the Insiders builds on my desktop.... |
Does it uses AveYo works ( https://gist.github.com/AveYo/c74dc774a8fb81a332b5d65613187b15#gistcomment-3921908 ) which doesn't require tpm at all? Or microsoft official guide: https://www.pcmag.com/news/microsoft-offers-tpm-20-bypass-to-install-windows-11-on-unsupported-pcs which requires tpm 1.2 at least? |
|
Can't use Microsoft's guide, since that only applies to upgrade from a running Windows to Windows 11. Like AveYo, we use the So that's I didn't apply the |
|
What about |
|
I haven't seen any evidence that this is a valid key. Do you have a source for that one? |
|
Just some guides listing it and on some forums, including MDL (it's part of the MSMG ToolKit). Not sure what their sources were. I don't have access to a CPU which would fail the check, otherwise I would confirm it myself. |
That's actually my problem. The references I see are from forum users asking "But what about a Especially, if you look at the AveYo script mentioned above, you'll see that this option is not being used, which leads me to think that it doesn't exist at all, else I'd expect the script, which is designed to bypass every possible restriction, to have it. |
|
Downloaded 3.15 and 3.15p from the official website (no store app) and got the same error message(s) that the OP had. Came here and downloaded 3.16 Beta #2 and was able to successfully create a bootable drive w/o any shortcut keys. Running Insider Preview build Windows 11 Pro 210929-1415 and working to built boot media to go to RTM. |
I did not try W11 yet, but know a guy that installed it on a Phenom II without |
|
@pbatard - Just curious - but has this been of any use for rufus? I'm guessing no as it either makes the user add a registry key for attempting an in-place upgrade, or else suggests to simply accept the warning to continue / use DISM to apply the update directly to an existing installation. Still, thought I'd ask instead of assuming. |
|
Not useful since this is for in-place upgrade as you correctly guessed. As a matter of fact, the "Ways to install Windows 11" provided by Microsoft on how to install Windows from scratch on unsupported hardware are severely lacking, since they aren't mentioning the |
|
There are other repos which use it, but again no sourcing or video evidence. Just seems odd that there would be I'll see if I can get hold of an old laptop from family. |
|
Well that was disappointing. Got my hands on an old laptop from 2012/13 with an i7 3630QM, and all that was needed to bypass the requirements page was Tried |
|
With the release of Rufus 3.16, I am going to close this issue, so that any remaining problems can be tracked against issues opened against the 3.16 release. |
|
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. |
Issue description
I cannot format any disk using Rufus when using Windows 11. I've used it on the same system while using Windows 10 without any problem. Also, I can manually format the device using diskpart and Windows without any problem. I've tried:
-Using several USB devices, none of them work while using Win 11.
-Using every single USB port, both from the PC Case and motherboard. None won't allow formating using Rufus on Win 11.
-Using Rufus on Win 10 with the same and diferent PC works properly, using the same devices to format.
Here's the capture of the error, and below there's the log file:
Log
The text was updated successfully, but these errors were encountered: