Sửa lỗi you cannot create a new volume năm 2024
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account Open MarekKnapek opened this issue Jul 1, 2023 · 22 comments Comments
Steps to reproduce
Expected behaviorNew container is created, containing volume formatted as exFAT 64k. Actual behaviorError appears, failed to format volume.
Work-around
The problem
Windows Server 2022 Standard, 21H1, version 10.0.20348.1787, amd64. The text was updated successfully, but these errors were encountered:
Thank you for this report. Normally, you should not see a UAC prompt because it is used only as a fallback when calling the When I have done some tests on the From here, there 3 things to do:
Meanwile, can you please help in understanding why format.com fails in your machine by doing the following:
what is the error you have?
This is exactly how VeraCrypt Format makes use for Thank you.
After reviewing the code responsible for this part, I found two ways to enhance it and make it more robust:
Moreover, I added better error management in order to display adequate error messages to the user in case of failure Here is the commit with this changes: 0bfed65 With this change, you should not have an issue but real test under Windows Server 2022 is needed to confirm. I'm planning to prepare a build today so it would be good if you can test it. Thank you.
I did as you said. Non-admin result:
Admin result:
Thank you for the test result. It is surprising that format.com fails with Access Denied error. Normally, it should succeed since the volume is mounted as removable media. Maybe a process is accessing the mounted volume as the message says. Anyway, with the new change, the fallback to FormatEx should work since it is run as admin and it uses the correct removalMedia type. A there will be error message displayed with error code in case of failure. As I said, I will create a new build and it would be helpful if you could test it.
I did some digging why
1 aka
2 function from
3 module. This function ultimately calls the
4 function from
5 module. It does it with
6
7,
8
9,
0
1,
2
3, and it fails with
4
5.
Hello @idrassi, I did some more digging. And I figured out that the formatting fails because Windows (for whatever reason) refuses
Impressive investigation, @MarekKnapek! Your dedication and analytical skills are truly remarkable. Concerning the integration of your changes into the main VeraCrypt codebase, there are a couple of potential issues I'd like to highlight:
As I mentioned earlier, I've already implemented a change that should resolve your issue. This involves falling back to a FormatEx API call (which triggers a UAC prompt) if formatting fails. Regrettably, I realized that I didn't share the link to access the Beta version that includes this change. You can find it in the Sourceforge Nightly Builds folder. I truly appreciate your efforts in analyzing this issue. If you're able, please try out the beta version and let me know how it works for you.
I still encounter this bug on: OS: Windows Server 2022 VeraCrypt Version: 1.26.7, Released Oct 1, 2023 FAT formatting completes, but attempting NTFS fails. Attempting to use FAT formatting during the VeraCrypt volume creation and then switching using Windows tools to format the drive also fails. I've also tried to run VeraCrypt as admin, to the same effect. My workaround has been to format the drive I want as NTFS first and then encrypt in place.
@jgonyea Your issue is worse than the one reported by @MarekKnapek since even admin privileges are not enough to allow formatting with NTFS. I guess that using "format.com" in an elevate command prompt also fails. What error do you have when invoking "format.com Z: /FS:NTFS"? This will help understand the nature of the failure. Thank you.
Ran into an issue similar to jgonyea’s. format.com would complain about partition size vs alignment or something. Unfortunately, I no longer have the exact error message around.
@itkfm: I've resolved an issue where A beta version, 1.26.10, including this fix, has been released and is now available in the Sourceforge Nightly Builds folder. I would greatly appreciate it if you could test this version and provide any feedback you might have. Thank you for your help.
@idrassi I can confirm, that VeraCrypt v1.26.10 fixed the issue in Windows 10:
Same problem here (Windows 11 with Storage Spaces) Running 1.26.10 x64 Format command on blank filesystem doesn't work either : "Format failed."
I would greatly appreciate it if you could test this version and provide any feedback you might have. I worked around the issue by creating a filesystem first and encrypting that then. Unfortunately, this was a client’s system and I no longer have a suitable/similar environment to test the updated version with. Thanks for the fix anyway.
Just did that, not working either : "Incorrect function" when I try to browse the disk. What is going on ?? |