Windows 10: I'm short 1 GB from formatting and can't upgrade to Windows 11

I was trying to upgrade to Windows 11. I have in the past on this computer, but I switched to a linux-based OS, and back to Windows 10. I am now trying to update back to Windows 11 when it says I only have 63 GB of storage, and I need 64 to upgrade. Is there a way to fix this or bypass it? Please help.

:)

 

How To Format A Write Protected Flash Memory ?

¿You already tried this one?...

Run CMD


1. diskpart
2. list disk

Then in the 3º step, put the correct number of disk in the list for the usb flash (if it's listed in disk 3, then you'll have to write select disk 3).

2. select disk #
3. clean
4. create partition primary
5. select partition 1
6. active
7. format fs=fat32
8. assign
9. exit

with that commands you will format the flash drive in fat32, if you have a large drive you can select also "format fs=ntfs" in step 7.

good luck!

 

Change of short date format

In the past, I have setup a GPO to configure the short date format (under Control panel -> Region -> Formats) to MM/dd/yyyy

It works for Windows 10 build 1603 up to build 1803.

Recently, I have some machines upgraded to build 1903, and found that the short date format was changed to M/d/yy instead during the machine startup. If I run "gpupdate /force" manually and can successfully changed it back to MM/dd/yyyy.

I tried to add GPO by directly modify the registry: (HKEY_CURRENT_USER\Control Panel\International\sShortDate), and the result is the same. After PC startup, after the group policy is applied (by system automatically), the short date format is reverted back
to M/d/yy

 

Change of short date format

Furthermore, I found that the registry key - sShortDate was mysteriously missing after the PC reboot (before PC reboot, it was still there). If this key is missing, then the default format of the short date will become M/D/yyyy (without the leading zero
for day and month).

My existing workaround is to add the timeout command to sleep for 60 seconds at the end of the login script. After the timeout, then run "gpupdate force" to set the key value. But this is NOT a solution. It's just workaround. It is at risk if the user close
the login script window before gpupdate is executed. we rely on the short date format in generating customer reports.