Are you having problems installing Windows on your target GPT or MBR drive? On this page, we’ll thoroughly discuss this issue in two parts and you can follow to find respective solutions toward different errors.
| Workable Solutions | Step-by-step Troubleshooting |
|---|---|
| Fix Can’t Install Windows on GPT Disk | Fix 1. Convert GPT Disk to MBR Disk using EaseUS Partition Master…Full steps Fix 2. Enable UEFI Boot Option in BIOS…Full steps Fix 3. Convert MBR to GPT via EaseUS Partition Master…Full steps Fix 4. Convert MBR to GPT using DiskPart…Full steps |
| Fix Windows Cannot Be Installed the This Disk | Fix 1. Convert Dynamic Disk to Basic Disk…Full steps Fix 2. Remove HDD Protection and Change SATA Controller Mode…Full steps Fix 3. Repair Your HDD…Full steps Fix 4. Format the Partition to NTFS…Full steps |
Check out and find the easiest solution to resolve your problem, installing Windows on your PC without any issue now.
Note that if you have saved important data on the target disk, back up your data first as some of the following fixes may remove data on your target drive.
Part 1. Fix «Can’t Install Windows on GPT Disk» Error
Applies to: Fix «Windows Cannot Be Installed on GPT Partition Drive’ or «Can’t Install Windows on GPT» error.
Problem: Can’t Install Windows on GPT Disk
«I’m trying to install Windows 10 on a new SSD, but the computer keeps giving me this message ‘Windows cannot be installed on this disk. The selected disk is of the GPT partition style.’ What does this mean? Do I have to convert the GPT disk to MBR? Or to enable UEFI boot mode in BIOS?«
You won’t be able to install Windows on GPT disk if you are receiving this notice from your PC as listed below:
Error 1. «Windows cannot be installed to this disk. The selected disk is of the GPT partition style.»
Error 2. «Windows cannot be installed on this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only installed on GPT disks».
Those two errors mean that the Windows cannot be installed on GPT drive. Don’t be panic. In the following, we’ll explain why you cannot install Windows to the selected disk and list practical solutions to help you out.
You May Also Like:
Why You Fail to Install Windows on GPT Drive
1. You forget to enable UEFI boot option. Or the motherboard supports Legacy BIOS only. (Error 1)
2. If you receive Error 2, you must learn something about UEFI and BIOS. Know the differences and relations between them.
Usually, when you install Windows on UEFI-based PC using Windows Setup, the target disk must be set up to UIEFI mode or BIOS compatibility mode. If your computer is booted in UEFI mode,while your target disk is not configured UEFI mode, you’ll met Error 2.
4 Fixes to Resolve «Cannot Install Windows on GPT Disk» Error
Here, we’ll provide you with 4 effective methods to fix this error issue and relative errors. Note that the former method is presented, the higher success rate it will be.
Fix 1. Convert GPT Disk to MBR Disk using EaseUS Partition Master [Error 1]
When the computer doesn’t support UEFI, you cannot install the Windows on GPT drive unless you convert the disk from GPT to MBR.
Professional partition manager software — EaseUS Partition Master can organize your hard drive and change the partition style easily. You can easily convert GPT to MBR with the help of this software, making disk available to install Windows again:
Step 1. Install and launch EaseUS Partition Master on your computer, go to the Disk Converter section.
Step 2. Select «Convert GPT to MBR» and click «Next» to continue.
Step 3. Select the target GPT disk that you want to convert to MBR, and click «Convert» to start the conversion.
Read Also: Windows 10 Won’t Install on SSD
Fix 2. Enable UEFI Boot Option in BIOS to Fix Windows Cannot Install on GPT Drive Error
If you are faced with Error 1 — «Windows cannot be installed to this disk. The selected disk is of the GPT partition style.», you can boot to UEFI mode if your motherboard supports UEFI.
Step 1. Reboot the PC and press the key that opens the boot device menu. You can press the Esc, F2, F9, F12, or another key to enter the boot menus.
Step 2. Boot into UEFI mode and locate the boot options menu.
Step 3. Confirm in the Boot Priority List that the USB UEFI OS Boot option is at the top of the list. Save your changes and continue to install Windows.
Fix 3. Convert MBR to GPT to using EaseUS Partition Master
If you encounter Error 2, you can fix the «The Selected Disk Has an MBR Partition Table» error by converting MBR disk to GPT disk.
On the UEFI system, Windows can only be installed to GPT disks or something similar. That’s because MBR is compatible with BIOS while GPT is compatible with UEFI.
The steps are similar to those of converting GPT to MBR. The difference is that you need to convert to GPT with the help of EaseUS Partition Master:
Step 1. Download and launch EaseUS Partition Master on your computer.
Step 2. Go to Disk Converter, select «MBR => GPT» and click «Next» to continue.
Step 3. Select the target MBR disk that you tend to convert to GPT, and click «Convert» to start the conversion.
You May Also Like:
Fix 4. Convert MBR to GPT using DiskPart
Aims to resolve Error 2.
Step 1. Turn off the PC and put in the Windows installation DVD or USB.
Step 2. Boot the PC from the DVD or USB.
Step 3. In Windows Setup, press «Shift + F10» to start Command Prompt.
Step 4. Enter the following command in order:
- diskpart
- list disk
- select disk
- clean
- convert gpt
- exit
Step 5. Close Command Prompt.
After removing «Can’t install Windows on GPT disk» error, you can now continue installing Windows on your PC. You can refer to Install Windows 10 on GPT disk for a detailed tutorial guide.
Part 2. Fix «Windows Cannot Be Installed the This Disk» Error
Applies to: Fix «Windows Cannot Be Installed to This Disk» Error.
Error: Windows Cannot Be Installed to This Disk
When you are going to install Windows 10/8/7, you might receive different kinds of errors saying Windows cannot be installed to this disk. Here are some common errors that you might receive:
Error 1. «Windows cannot be installed to this hard disk space. The partition contains one or more dynamic volumes that are not supported for installation».
Error 2. «Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure the disk’s controller is enabled in the computer’s BIOS menu.»
Error 3. «Windows cannot be installed to this disk. The disk may fail soon. If other hard disks are available, install Windows to another location.»
Error 4. «Windows cannot be installed to the hard disk space. Windows must be installed to a partition formatted in NTFS.»
Why Windows Cannot Be Installed to The Selected Disk
Why you could receive these errors? What are the main reasons? According to the error messages, the main reasons are as follows:
1. Users can only make a fresh install on a dynamic volume only when the volume was converted from a basic disk and was a boot partition or system partition. (Error 1)
2. Hardware protection and SATA Controller mode could bring up Error 2.
3. If you get Error 3, you can take your hard disk failure into account.
4. An incompatible file system of the partition to be installed with Windows. Microsoft rules that Windows must be installed to a partition formatted in NTFS since Windows Vista. (Error 4)
You can now selectively choose one of the solutions to fix Windows cannot be installed to the disk issue on your own PC.
Fix 1. Convert Dynamic Disk to Basic Disk
If you receive Error 1 — «Windows cannot be installed to this hard disk space. The partition contains one or more dynamic volumes that are not supported for installation», convert dynamic to basic disk.
EaseUS Partition Master also helps you convert dynamic disk to basic disk easily and quickly.
Here are the detailed steps:
Step 1. Install and open EaseUS Partition Master and go to Disk Converter.
Step 2. Select the disk conversion mode that suits your need:
- Convert Basic to Dynamic: change a Basic disk to Dynamic.
- Convert Dynamic to Basic: change a Dynamic disk to Basic.
Step 3. Select the target disk — Basic or Dynamic, confirm you’ve select the correct disk and click «Convert» to start.
Convert Basic to Dynamic Disk
Convert Dynamic to Basic Disk
Fix 2. Remove HDD Protection and Change SATA Controller Mode (for Error 2)
If you receive this message «Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure the disk’s controller is enabled in the computer’s BIOS menu.» — Error 2, you should do two things:
Phrase 1. Remove Hard Disk Protection
Check if your hard disk protection is enabled. If it is, contact the salesperson and remove the protection according to his instructions.
Here is a quick guide that you can follow to remove write protection from hard drive using DiskPart:
Step 1. Start > Run -> type CMD and press enter.
Step 2. Type diskpart and press enter.
Step 3. Type the following command lines and hit enter each time:
- list volume
- select volume # (# is the number of your HDD.)
- attributes disk clear read-only
- clean
Step 4. Type exit and hit Enter. Close DiskPart to finish the process.
After this, you’ve successfully removed write protection from your hard drive. If you need more practical solutions, refer to How to Remove Write Protection on SSD for help.
Phrase 2. Change SATA Controller Mode
This error may indicate that the BIOS settings of your computer are not properly configured. Make sure you have changed the SATA Controller mode in BIOS. Then, you can try setting BIOS to the factory and go back to the default setting.
Fix 3. Repair Your HDD to Fix «Windows Cannot Be Installed to the Hard Disk Space»
Error 3 — «Windows cannot be installed to this disk. The disk may fail soon.» occurs when there’s something wrong with your HDD. What to do with a dying HDD? How to repair it? You should stop Windows installation and then clone or back up important data immediately. Then, you can start repairing your HDD.
Also read: How to Repair HDD without losing data
Fix 4. Format the Partition to NTFS
This method aims to solve Error 4. When partitions on the target disk are not with the NTFS file system, Windows cannot be installed to the disk.
Changing a volume’s file system is not an easy task for those who are not familiar with computer management and command line. Thus, an easy and safe solution is needed.
Comprehensive partition manager software — EaseUS Partition Master can fully meet this requirement. It enables you to format HDD to NTFS easily.
For this case, you need to create a bootable drive and then format hard drive from USB.
After fixing Windows cannot be installed to this disk or GPT/MBR drive error, you can then continue installing Windows on your target disk in your PC.
Manual Service for Fixing ‘Can’t Install Windows On GPT’ or ‘Windows Cannot Be Installed’ Error
Alongside following the above-provided solutions, you still have another option, which is to customize a manual service and let EasUS experts resolve this issue for you. You no longer need to worry about taking a wrong step while following the guidelines above. Everything can ben efficiently resolved and Windows can run on your GPT disk successfully.
EaseUS experts are available to provide you with 1-on-1 manual services (24*7) and help fix different Windows configuration issues. Our experts will offer you FREE evaluation services and efficiently diagnose and resolve Windows update errors, Windows installation, or daily OS issues using their decades of experience.
- 1. Fix Windows update errors, such as update failure, unable to upgrade Windows, etc.
- 2. Serve to download and install the latest Windows operating system on PC with success.
- 3. Provide fixes for daily Windows system errors with drivers, permission, account settings, etc., issues.
Conclusion
This page covers 4 fixes to get rid of «Can’t install Windows on GPT disk» error and 4 practical methods to remove «Windows cannot be installed to the drive» error for all levels of Windows users.
If you are faced with any one of the errors, you can find answers here. If your target disk has unsupported partition styles disallow you installing Windows on it, EaseUS Partition Master helps convert GPT to MBR, Convert MBR to GPT, and even change Dynamic to Basic disk.
This software plays an important role during the fixing process. Why not get it now.
Extended Reading: Cannot Install Windows FAQs
Besides the above issues, if you have further concerns about installing Windows on GPTor MBR disk, check the questions and answer below.
You may get a clue:
1. How do I fix Windows cannot be installed to this disk MBR?
How do you fix ‘Windows cannot be installed to this disk’? The solution is easy to conclude: change MBR to GPT.
Here are two methods that you can try:
- Method 1. Change MBR to GPT using EaseUS Partition Master (as presented on this page in Fix 3 Part 1)
- Method 2. Run DiskPart to change MBR disk to GPT (as presented on this page in Fix 4 Part 1)
2. Can GPT boot into Windows？
Yes. GPT can be used to boot Windows OS as long as you have a Windows system installed on the disk or you have migrated your computer operating system on the disk.
If you need a guide to migrate OS to GPT, follow this link for help: How to Move Windows 10 to Another Drive (HDD/SSD).
3. How do I change GPT partition to BIOS?
Mostly, GPT partition supports UEFI boot mode and BIOS compatibility mode. In order to change GPT partition to Legacy BIOS mode, you need to follow the following tips:
- #1. Check if your computer motherboard supports BIOS boot mode. (Check BIOS)
- #2. If the motherboard supports BIOS boot, then you need to check if your disk is with the MBR partition style.
- If not, convert GPT to MBR disk using provided method on this page in Part 1.
- #3. Install Windows that support BIOS boot on the disk.
- #4. Finish Windows installation, enter BIOS and set the computer to boot on the MBR disk which was with GPT partition.
- #5. Save the changes, and restart PC.
Теперь Microsoft предоставляет значения хеш-кода SHA256, чтобы подтвердить, что ISO-файл Windows 10 оригинальный, не был подделан, поврежден или изменен, и вот как проверить загрузку.
Проверка хеша в Windows 10.
Начиная с версии Windows 10 2004 (обновление за май 2020 года), Microsoft начинает предлагать хэши, которые помогут вам проверить целостность данных и подлинность загруженного файла ISO для Windows 10.
Хеш — это математическая подпись (текстовая строка), которая рассчитывается с использованием криптографического алгоритма (SHA-1, SHA-256, MD5) для данных фрагмента. Если какое-либо изменение произойдет после того, как контрольная сумма была вычислена, значение хеш-данных также изменится.
В этом случае хэши SHA256, которые предоставляет Microsoft, позволяют использовать PowerShell для проверки того, что загружаемый ISO-файл Windows 10 не был подделан или поврежден.
В этом руководстве вы узнаете, как проверить целостность и подлинность файла ISO Windows 10 версии 2004.
Как проверить, что Windows 10 ISO не был поврежден или подделан.
Чтобы проверить контрольную сумму ISO для Windows 10, выполните следующие действия:
Шаг 1: Откройте Проводник.
Шаг 2: Перейдите к папке, содержащей файл ISO Windows 10.
Шаг 3: Введите следующую команду в адресной строке и нажмите Enter:
powershell
Шаг 4: Введите следующую команду, чтобы проверить SHA256-хэш ISO-файла Windows 10, и нажмите Enter:
Get-FileHash .\Win10_2004_Russian_x64.iso
Совет: в данной команде обязательно измените имя файла (Win10_2004_Russian_x64.iso), соответствующим вашей загрузке.
Подтвердите результат хеширования на основе хешей, предоставленных Microsoft.
Например, D4CDA51B4F4B61E3D82A6EF04B8860F93C62FFA48D387A9AC28855C2E9CFC5BD должен быть результатом контрольной суммы при проверке файла ISO для 64-разрядной архитектуры Windows May 2020 Update (на Русском языке), а 58665BFE9DAF754708A8C6D8348BFA46C26D7017EB78F5C425589ADB70393C64 результатом контрольной суммы при проверке файла ISO 64 бита Windows May 2020 Update (на Украинском языке).
Если выходные данные совпадают, то вы можете быть уверенны, что файл ISO не поврежден и является подлинным.
Windows 10 версия 2004 SHA256 хэш-значения.
Вот список значений хеш-функции для каждой архитектуры и языка Windows 10 версии 2004:
-
Arabic 64-bit: 869BA1848C444140C87A6995A136ED8CD7F14DFE69907023BACF430229770D02
-
Arabic 32-bit: 0BA24CF7E94FBFDC0666FE01D082EEFCDB48940D2462C8C584E237CB7B42DA05
-
Bulgarian 64-bit: B6C88B2CB1618C83D2DB59DC79BB4935F8EFC3DC5279AE9C7A4A6B2D7B62A6A0
-
Bulgarian 32-bit: 211D2044E4A90C363E76EABF395EBF6638560F06655C5C397C2525D317787E24
-
Chinese Simplified 64-bit: E04E4B96B2CBE7A2AFE4889630958B46CD70F5DFF39A8283E8AD106C3D2F75B5
-
Chinese Simplified 32-bit: 325D3B31FFB86586572997CF036A615244AC073879F977BFB0F0467E5F0B5169
-
Chinese Traditional 64-bit: 4975BB3A9BB0FEA8DA772E366836E48E33EBA4DB0E7513C1E0F3A3087607C439
-
Chinese Traditional 32-bit: 25ACE770E8FD366AE0C861B0E01561CB5DEBD537ABB181584EE7EF16938022EF
-
Croatian 64-bit: 497151C206697842712A63637ED702A1AF05CBEC73A728D8CD341BBA1FCC9ACF
-
Croatian 32-bit: 4F6178F8FB17E8D0AAB2554355D68D05AFA918402B2B5762F72F68EC4B553D61
-
Czech 64-bit: 673927697D64316CCA7BE258ABFA07F6C861317B404D10AA6A77EBDB1395026F
-
Czech 32-bit: F9F8F881F8F71D3186C3963BDD85A734C0634EAFEDACC7E4C461A12C2C31893A
-
Danish 64-bit: 2281062E4013AAD18320B53A8192D0F0C03C7A0D2D12F674E9BC8FE0E0B3C59E
-
Danish 32-bit: A6D29392006DD9629640F39B4AD1BC92B81C9116EC15AEC59713D6D99770543C
-
Dutch 64-bit: 059D59BFB72260DEC0981C0747190FEB6FA7911E6653F071FACE0B91490FE84A
-
Dutch 32-bit: D37E044F03F5C27164731213C19B08C4655ACAE3D55B4D1D82867ED1675E7D6A
-
English 64-bit: A9EFD2329ED805A6A58E0E0101F9B22AD4031E80E2C663C571CD004DB26D2F31
-
English 32-bit: 34DEDA035093417D811DBE4A6EB4CCB6A5D9E86F586395C93DE3C73D5D9B5D2B
-
English International 64-bit: 4D7D73409B36E44462C690EC58AE0DC6846B01307799432FBD542388D4AD30E7
-
English International 32-bit: 982E7E93B31CB5790DAEF5CB4C48A0A18A993333C43AEEC94970883E049BA324
-
Estonian 64-bit: EC0991DE5189D54312B93AE61187836299C109C167D48C3BDF9771AC5CC4402B
-
Estonian 32-bit: C33BCAA592C563636B5C69517F3904E7D0436ED9FDA5201756C5694A48AA6E2A
-
Finnish 64-bit: 35008D60E05E99A27D8FFD0F9BF91CA0CF1ABD293AD02A8A4B6A6680567498F9
-
Finnish 32-bit: C5276BD1580EE4FA9D23B27D6108DA0CDEA36FA972AE51BCF850F622221A2539
-
French 64-bit: 567EAB53626F7865F93D96BDCCC61C5D63F5B95F6CC9C82CA6AABF5282BEED90
-
French 32-bit: B717494E2C8D63E7DA0A1537A45EC5EE0F3C4F3DCAD488AD444A0779DAF3B8B3
-
French Canadian 64-bit: 84F7792CF7C2F5CBF963C54494FD4B51F097F201B93E4DFC966A21D9EE262A68
-
French Canadian 32-bit: 8FE59E2E703952F4EC58AC084EC7F9DB48B647B8101631DF8FA741275B849061
-
German 64-bit: 17C710909A722392A32B3A4364471838588C2F408B4B6DBCDCE990F0547F1074
-
German 32-bit: 83C5C496424BB6D8775C5AFEA92DD893E4DBB7AE2D6DA0BEFC85605B77AD5178
-
Greek 64-bit: E8B637253D1CD4EE6AA0C1562C1AE5C80C7250614D35FB39A4B6D1CB431B80A5
-
Greek 32-bit: 3FD3717399E2223401AAF0F14DF68139488AD3F80567954FB12C5C94F01F2432
-
Hebrew 64-bit: EE314732FBBB9EB2A8E58B32F63747432C9C45317EAD06E46E037B25F90CF618
-
Hebrew 32-bit: 6AB6B03E2AC85609F7F80970B622EBED4C3E0D3893FFC77D6B7F76BCC94DC5CC
-
Hungarian 64-bit: 0EA3DD7EECF65BA355E0961311B5659C13474B36F3A517F336D34D7E1A4C7139
-
Hungarian 32-bit: E49CF557B7CBF072BBCF1CD35271B37CCAF87819670290ECDE30DE1FD6B0E888
-
Italian 64-bit: CA6DE4BF66E1DBB83612D6DD34E554403DB1208439D8F28EC151565E4A9F4028
-
Italian 32-bit: DB3D52F36B1E718C9B01AA3761F75C107A9D5922705D45C9E89C166ABD0B7B14
-
Japanese 64-bit: 6FEC5075735660F482405C2AA0283EA76C70F88AAAE20E05A26E836B95BB8998
-
Japanese 32-bit: A33266C617E21FCE9D29A43684866EF3C9A24ACB3B48806A9729CAC099C96189
-
Korean 64-bit: DC03ECB2B5090BB219DE90091361CCFA0E5310C5EDCDEE9A0EAE3E42BE81804E
-
Korean 32-bit: 7DB4E81418210C79CE6AF9D85FB6E48ECAAB37D1DBB35B5156DCEA8C82C5706D
-
Latvian 64-bit: 06379A910F38AC29C7A81961049B1381E7FD8CA53BB4F1BABB07692DC932ED95
-
Latvian 32-bit: D36E4B6688259E7651C5EEEA6B97A7E48D07049AE2EB87D5B5CE20CAE48EECE7
-
Lithuanian 64-bit: C9374915B6E6695EABCF8EAD5F4335B58D47EB2A4096B74198CF8ADE7FE33720
-
Lithuanian 32-bit: A58EDDC8B2ACD78A3B418E7FC5DB831350D6776953E119D5F0476544186162BC
-
Norwegian 64-bit: 248EB95D23A5B06203C2ED605F9AC3BF778EC3953DA7AF76C3F5B38F6DB59198
-
Norwegian 32-bit: 956F5CA9EDD36880C9CDE425B11BD710F1440A3BEDE4071246A927BAE5F49E92
-
Polish 64-bit: EF21D12C098017615BFC9A325A7244576654C4C6834934CB6D1658AB981D6501
-
Polish 32-bit: 2B646F0566745600216B76BE163C409B1A8DEB2205CABEBA8A12DBD2961F4E8E
-
Brazilian Portuguese 64-bit: 9F8AB79DCC6628C6DF6EC633890EA841AB2446BA25A414E7BD947D75BAC82CCD
-
Brazilian Portuguese 32-bit: 9D121F073AA068BAFD8B6425C721CB8D923C76A8BD9714D9723B195726BD5BF0
-
Portuguese 64-bit: 81D02C6B6553A842DFEB28EA3A4E1C7714DC9CA1852FC0F348FE8047AD822EF0
-
Portuguese 32-bit: 2E8945C774C9D47DDBC7B4E244E15DE869D534D1F834856A04C93DD79477C3E0
-
Romanian 64-bit: 8C505C9203516CCDE25429683CEFFA706ABE29DB507FDED344EFCDC58592BF7A
-
Romanian 32-bit: 18A621A73EB68D8B04F46BB5023D182F1A96C84D72371C63A23926A82CC8AA43
-
Russian 64-bit: D4CDA51B4F4B61E3D82A6EF04B8860F93C62FFA48D387A9AC28855C2E9CFC5BD
-
Russian 32-bit: 0DC53C74F861938E47490861DC1AA4F917BD4C567173C1B43B14B9999E363B0C
-
Serbian Latin 64-bit: 261494434A95D5A03F251AF32A52621A5ABA6776DC84B2ED6D748C862F0B14FA
-
Serbian Latin 32-bit: 748E16E39CF61EEC0999FFE10C420A0DC071038CDD379895966AC2C4BD16DC68
-
Slovak 64-bit: 6E9B813E01032B0D22D682EB9914CB1C4E4880797B11A98E808788ABDB653948
-
Slovak 32-bit: E4906F6F7A6FAD9675106463D76C2A78AD77107F8CFD86BCD4595C50D95C0E70
-
Slovenian 64-bit: 35174A0080D1EAA8CD619591E54ED10E4D5549166F029BF7A6729EEF2532F7FB
-
Slovenian 32-bit: 779A879244063C9BBE11EC02F17383AD265F11D775C3C001DC23E8818F14820A
-
Spanish 64-bit: 443CFA90E2D0A8FCA281294997C9C9CA605D33FC78A010B39F04728E64C0B343
-
Spanish 32-bit: 7C14C8FA47E48D24E9CD777DF6B079352CB6F37079382645875569DDBEBA1964
-
Spanish (Mexico) 64-bit: 78814BF445C237F58556B18008FDAC64E32B16B2400C04EE17BFA79E8CC4319A
-
Spanish (Mexico) 32-bit: D0A86807136F13B3EB483A524DBCB156CDFF573036F3330D5FB7975BE812F31F
-
Swedish 64-bit: 29943DF2747F37CF20FE3D08D729F50638486A8E0D95366227A0C5B6427337FC
-
Swedish 32-bit: E916B76AF280E14FD00CF2D067A14D9A0B14E76AFF60853EC80C8115DD48CE48
-
Thai 64-bit: DC897C2AF3AEADA082B28A34B7852D906EAACE00CA232A1F759CAC878CDD9AC1
-
Thai 32-bit: 6EFEA4AA404044C941D7D0B001583808500CF5BCA890A359AB1E6D9DF3F9B754
-
Turkish 64-bit: E099123E84BAD6C89431ABABB6F00A67989E5257D33815B32304D6095D38F50F
-
Turkish 32-bit: AE29E2B65CB52DE482F1BD2204D28CD47A94A02B9D6C85713025AAE1D1893625
-
Ukrainian 64-bit: 58665BFE9DAF754708A8C6D8348BFA46C26D7017EB78F5C425589ADB70393C64
-
Ukrainian 32-bit: 61AE0D59D4B0061930A2CC63C9D738A2620CA6D4A09072B2B663000A3437B38E
Microsoft предоставляет хэш-значения при использовании этого метода для загрузки файла ISO Windows 10.
При скачивании образов ISO Windows 11 и 10 со сторонних сайтов, даже если они обозначены как оригинальные, у некоторых пользователей может возникнуть вопрос: а действительно ли это так?
Ответить на этот вопрос сравнительно легко, сверив контрольную сумму образа с контрольными суммами оригинальных образов, о чём и пойдёт речь далее в статье.
Определение контрольной суммы SHA-256 образа Windows
Для любого файла можно посчитать контрольную сумму или хэш, подробнее о которой в инструкции Как узнать контрольную сумму файла в Windows. Контрольную сумму можно определить по нескольким алгоритмам, для каждого файла (набора байтов) она будет уникальной и именно с её помощью можно определить оригинальность образа Windows.
Всё, что потребуется — узнать контрольную сумму SHA-256 для файла ISO и сравнить её с контрольной суммой для оригинального образа. Для подсчета достаточно выполнить следующие шаги:
- Запустите Терминал Windows или Windows PowerShell, сделать это можно в меню по правому клику на кнопке «Пуск».
- Введите команду
Get-FileHash "путь_к_образу.iso"
и нажмите Enter.
- Дождитесь завершения вычисления контрольной суммы (может занять некоторое время, поскольку обрабатывается не малый по размеру файл).
Теперь у вас есть хэш SHA-256 вашего образа ISO, что с ним делать дальше? К сожалению, официальных списков контрольных сумм Windows на сайте Майкрософт нет (кроме версии Enterprise), но вы можете использовать один из следующих методов:
- Скопировать полученную контрольную сумму (выделить в окне PowerShell, нажать правой кнопкой мыши, выделенные символы окажутся в буфере обмена) и выполнить поиск в Интернете. Для оригинальных образов вы с большой вероятностью найдёте её в сторонних список вариантов образов и их хэшей. Например, для актуальной на момент публикации материала русской версии Windows 11 ISO контрольная сумма —
0812CAA1BB47BFB916EE66D34EA9A8E673CC1AA200212483FC54CED0D885FC99
и она легко находится в сети.
- При загрузке образа с официального сайта с подменой агента браузера или при открытии официального сайта с устройств, на которых установлена не ОС Windows (второй способ в этой статье, аналогично для Windows 11 и 10) после выбора версии, языка и нажатия кнопки «Подтвердить» ниже списка образов будет ссылка с информацией о проверки загрузки (Verify your download), включающая контрольные суммы SHA-256 для актуальных образов на разных языках. К сожалению, сейчас этот метод не работает для пользователей из РФ по причине блокировки загрузок для них.
Учитывайте, что описанное сработает для образов, которые были скачаны именно как готовые образы ISO. Если же вы создавали ISO с помощью Media Creation Tool, вы можете быть уверены, что он оригинальный (при условии, что сама утилита скачана с официального сайта), но вот контрольная сумма у него будет отличаться от таковой для известных оригинальных образов.
Причина в том, что утилита скачивает отдельные файлы, из которых затем «собирает» образ и итоговый файл ISO может каждый раз отличаться (если сравнивать их по байтам), кроме этого, в зависимости от способа загрузки ISO в образе может находиться файл сжатый install.esd или не сжатый install.wim, что также делает файл отличающимся.
Итак, вы долго и упорно загружали образ Windows, а теперь хотите убедиться, что по дороге не потерялось ни байта. Или дистрибутив вам принесла добрая фея, и вы хотите проверить, не связана ли она с пиратами. Для определения целостности дистрибутива вам понадобятся две вещи – контрольная сумма и программа для ее проверки.
В 2017 году Microsoft перенесла загрузки с MSDN на новый сайт https://my.visualstudio.com/downloads, где долгое время было невозможно посмотреть контрольную суммы дистрибутива без подписки. Приходилось пользоваться поиском на сайте https://msdn.rg-adguard.net/. Но все-таки это не первоисточник.
Однако в какой-то момент вернули возможность просмотра контрольных сумм на сайте https://my.visualstudio.com/downloads после входа с учетной записью Microsoft.
/blog/wp-content/uploads/windows-checksum.mp4
Это – половина дела.
certutil
Утилита входит в состав Windows 7 и новее.
certutil -hashfile [путь к ISO]\имя_файла.iso SHA1
Результат:
Утилита поддерживает хэш-алгоритмы MD2 MD4 MD5 SHA1 SHA256 SHA384 SHA512, любой из которых можно указать в качестве параметра. Подробная справка по команде:
certutil -hashfile -?
File Checksum Integrity Verifier (fciv)
У Microsoft была собственная утилита командной строки для вычисления и проверки контрольной суммы файлов — File Checksum Integrity Verifier (fciv.exe). Она никогда официально не поддерживалось, но ее можно было загрузить из KB841290 (ныне удалена). Здесь она по прямой ссылке (41 кб). Далее я предполагаю, что вы знаете, куда распакована утилита, и где сохранен ISO-образ Windows.
Достаточно выполнить одну команду в командной строке (Пуск — Поиск — cmd):
<путь к утилите>\fciv.exe –sha1 <путь к ISO>\имя_файла.iso
Например, если утилита на рабочем столе, а ISO-образ в корне диска D, команда будет выглядеть так:
%userprofile%\desktop\fciv.exe –sha1 D:\en_windows_7_ultimate_x86_dvd_x15-65921.iso
А результат – контрольная сумма файла:
Увеличить рисунок
Если не указывать параметр -sha1, утилита вычислит хеш MD5.
Как видите, все очень просто! Вы можете использовать этот способ для проверки контрольных сумм MD5 или SHA1 любых файлов.
Бонус: PsFCIV — модуль PowerShell для проверки целостности файлов на больших файловых ресурсах.
HashTab
Если командная строка вас пугает, можно проверить контрольную сумму более простым путем.
- Загрузите и установите программу HashTab.
- Щелкните правой кнопкой мыши на файле образа и выберите пункт «Свойства».
- Перейдите на вкладку «Контрольные суммы» (File Hashes).
Table of Contents:
How do you fix Windows cannot be installed on this drive? The message Windows cannot be installed on this drive typically appears during the Windows installation process, indicating that there is an error preventing you from continuing the Windows installation. In addition to the error, there can be another message appearing along with it, providing additional information. And the accompanying error message varies depending on the underlying cause of the issue, and thus it is useful to read the error message to get clues to solutions. The error message can be caused by several reasons, such as, improper file system format, incorrect partition table type, insufficient disk or partition size, bad sectors, wrong BIOS/UEFI settings, etc.
You can follow troubleshooting mentioned below to identity and fix the error. It is important to back up any data you don’t want to lose before making changes to the drive, because some solution involves deleting or formatting data and partitions. It’s always a good idea to keep backups for important data.
Fix 1: Windows cannot be installed to this disk. The selected disk is of the GPT partition style.
You may receive the error message »
The selected disk is of the GPT partition style
» when installing Windows OS to a GPT-style disk, see picture below. You will ask why Windows cannot be installed to this GPT disk. Generally, the main cause is motherboard. There are two types of boot modes: BIOS Boot Mode and UEFI Boot Mode. Most Windows versions have UEFI (Unified Extensible Firmware Interface) boot mode, while some versions since older days of Window XP have BIOS (Basic Input Output System) boot mode. Due to different boot modes, there are two types of partitioning schemes: MBR (Master Boot Record) and GPT (GUID Partition Table). If you want to boot system from a GPT disk, the motherboard should support UEFI; while on BIOS you should use MBR partition table. Thus, if you install Windows on BIOS system, the GPT partition table comes in your way. The installation will be blocked by the error.
Solution #1: Configure BIOS settings (boot mode)
First of all, you should ensure the Boot Mode in your BIOS is set to Legacy BIOS instead of UEFI. At present, most motherboards support both legacy BIOS boot and UEFI boot. Thus, you need to make sure the proper boot mode is selected in BIOS setting. The picture shows the boot mode is modified to Legacy. Please note that the BIOS menu may look different on your computer, as it varies based on the models of the motherboard on your computer.
Solution #2: Convert the GPT disk to MBR without losing data
Since Windows cannot be installed on the GPT disk, you can fix the error by converting the GPT disk to MBR format. The converting does not deleting existing partitions and files if you use third-party free partition manager software to finish the task.
DiskGenius is free partition manager software for all Windows users and it is able to convert GPT disk to MBR without risking any data loss. If you prefer a user-friendly alternative to the Command Prompt,
DiskGenius Free Edition
is an excellent choice, as it is easier and safer to use. Additionally, this partition tool enables you to create a WinPE bootable USB disk, allowing you to manage your disks and partitions even if your system fails to boot. Furthermore, DiskGenius can assist you in backing up your data, imaging your system, recovering lost data or partitions, and backing up your partition table, migrating Windows 11/10 to HDDs or SSDs, etc.
Step 1. Download, install and launch DiskGenius from your computer. If your computer cannot boot to system, you can
create a bootable USB disk
to boot computer, and then carry out rest tasks.
Step 2. Select the GPT disk to be converted and click «Disk» menu to choose «Convert to MBR Partition Table«, as below:
Step 3. Click Save All button from toolbar and click «Yes» from pop-up message box to save changes on partition table.
Tips: If capacity of the GPT disk is larger than 2TB, system can only make use of 2TB after it is converted to MBR.
Solution #3: Clean up the disk and convert to MBR using Command Prompt
It’s important to note that the conversion from GPT to MBR using Command Prompt will result in data loss on the disk, as the process involves deleting all partitions and data on the disk. it’s strongly recommended to back up all important data from the disk to a separate storage device to prevent data loss before trying following steps.
Step 1. Backup all of your data on the GPT disk you want to convert, as the process will erase all data.
If you can’t afford to clean the disk or do not want to take efforts to back up data, you can convert GPT to MBR following steps in Solution 2 which does not disturb existing data.
Step 2. Run Command Prompt.
Boot computer from the Windows installation disk and click «Repair your computer» when you see following screen.
You will then be directed to the Advanced Recovery mode and see the Troubleshoot screen. The click Advanced options > Troubleshoot > Command Prompt.
Step 3. Type diskpart in the command prompt and press Enter.
Step 4. Type in list disk and hit Enter key to view which one is of GPT style. The GPT disk is marked with asterisk in the GPT column. Remember the disk number you need to clean and convert.
Step 5. Type select disk # (# is the disk number and you should replace it with the actual number in your computer) to select disk.
Step 6. Type clean and press Enter.
Notice: this step will completely clean up selected disk, and all partitions and data will be deleted. Please make sure you have a backup before performing this command.
Step 7. Type convert mbr and press Enter, and the disk will be converted to MBR. Then you can execute exit command to exit or continue creating partition on this MBR disk.
Fix 2: Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.
When you attempt to install Windows in UEFI mode on your computer, you cannot select the disk you want. You may click Show details to view the reason which says »
The selected disk has an MBR partition table
. On EFI systems, Windows can only be installed to GPT disks». That means you cannot install UEFI mode on a disk using MBR partition table and it can only install to GPT disks, as image below:
GPT (GUID Partition Table) was introduced as part of UEFI which is the acronym for Unified Extensible Firmware Interface. Compared to the traditional MBR partitioning scheme, GPT offers a more flexible approach to disk partitioning. Partitions or volumes are contiguous areas on a physical or logical disk, visible to both the system firmware and the installed Windows operating system. The system firmware controls access to partitions before the operating system boots, and once booted, the partitions are managed by the OS.
Many modern computers support the UEFI version of BIOS, which speeds up boot and shutdown speed as well as provides security features. If you want to boot computer in UEFI mode, the disk installs operating system should be of GPT style. Many computers are able to use UEFI and they also provide CSM (compatibility support module) so that legacy version of BIOS can be used in necessary. The GPT drive format allows users to set up drives larger than 4TB and does not impose a limit on the number of partitions.
Solution #1: Change BIOS Boot Settings
The first try to solve the problem should be going through BIOS and changing UEFI boot settings. You can manually switch boot mode to legacy BIOS compatibility instead of UEFI mode.
Step 1. Restart computer and enter BIOS by pressing the specified key prompted by your motherboard manufacturer.
The prompt appears on screen before computer boots into Windows.
Step 2. Go to Boot tab and locate boot order option. Then disable EFI Boot Source and change boot mode to Legacy.
Step 3. Save changes and exit.
Solution 2: Convert MBR disk to GPT using DiskGenius Free
DiskGenius Free Edition is able to convert an MBR disk to GPT without losing data and the process is quite easy to follow:
Step 1. Install and launch DiskGenius Free. You can download this free partition manger software from the download center.
Step 2. Locate and select the MBR disk to be converted to GPT and click «Disk» menu to choose «Convert To GUID Partition Table«.
Step 3. Click «OK» button on the message box. Then click «Save All» button to make the converting work
When the disk is converted to GPT, you can retry installing Windows again and check if the error is fixed.
Fix 3: Windows cannot be installed to this hard disk space. The partition contains one or more dynamic volumes that are not supported for installation.
The «The partition contains one or more dynamic volumes that are not supported for installation» error is likely to appear when you attempt to install Windows on a dynamic disk. Users are allowed to make a fresh Windows installation on a dynamic volume only when the volume was converted from a basic disk and retained an entry in partition table. However, simple volumes (except system or boot volumes before conversion) that have been converted from basic disks do not have an entry in partition table, thus the installation will end up with the following error.
What is basic disk and dynamic disk? A basic disk is a storage type mostly used in Windows operating system, providing a solution to accommodate an array which changes storage requirement scenarios. A basic disk consists of partitions, such as primary and logical partitions, which can be formatted with a file system to store data. Generally, basic disks use MBR partition style since the disk is used by Microsoft MS-DOS operating system and all versions of Windows. Also, it supports GPT partitions on systems that support it. With basic disks you can create and delete primary, extended and logical partitions as well as format a partition or mark it as active.
On the other hand, a dynamic disk offers additional features not found in basic disks, for example, it is able to create volumes crossing multiple disks and create fault-tolerant volumes. Either MBR or GPT partition table styles can be used by a dynamic disk. Dynamic disks provide greater flexibility for managing volumes by utilizing a database to track information for volumes and other dynamic disks. Additionally, dynamic disk volumes can be created on noncontiguous scope or physical disks, while volumes on a basic disk should be located on a contiguous area on a single physical disk.
Solution #1: Convert the dynamic disk to basic disk in Disk Management
Step 1. Back up all volumes and data on the dynamic disk to be converted to basic, as this converting method removes all partitions and data on the disk.
If you don’t want to spends too much effort on data backup and transferring, you can try Solution 3 which can do the converion without deleting data.
Step 2. Open Disk Management. Right-click the Start menu (the Windows icon) and click «Disk Management».
Step 3. Delete all volumes on the disk. Right-click each volume on the disk you want to change to basic disk and select Delete Volume.
The disk will be converted to basic automatically after all volumes are deleted from the disk. If the converting does not happen, then move to step 4.
Step 4. Right-click the disk and select Convert to Basic Disk. Once the disk is converted to basic disk, you can create partitions on the disk.
Solution #2: Change a dynamic disk to basic disk using command line
Warning: If you want to keep your files on the disk, back up files or copy data to another disk before starting following steps.
Step 1. Open Command Prompt. If there in not operating system on your computer, you can use a Windows installation CD or bootable disk to boot computer and open CMD.
After the computer boots from the installation disc, choose «Repair your computer» and then access «Troubleshoot» to locate «Command Prompt».
Step 2. Delete all volumes on the dynamic disk by typing following commands with pressing Enter after each command.
diskpart
list disk
select disk # (# is the number of the dynamic disk)
detail disk
select volume 0
delete volume
To delete other volumes, you can continue typing «select volume 1» -> «delete volume» one more time.
Step 3. After all volumes are deleted, type convert basic and the disk will be converted into a basic disk.
Solution #3: Convert a dynamic disk to basic disk without data loss
Both methods above require you delete all volumes and data before converting, thus you should make sure there are not important data or you’ve created a full backup beforehand. Here is an alternative solution which is able to complete the conversion without losing data. DiskGenius is a professional dynamic disk converter, it is able to convert the dynamic disk to basic without deleting volumes within several seconds. Let’s see the entire converting process.
Step 1. Run DiskGenius and you can see the dynamic disk on the main interface.
Step 2. Locate and right-click on the dynamic disk and select Convert to Basic Disk option, as below:
Step 3. Click OK button from the pop-up message box to make the changing work.
Fix 4: Windows cannot be installed to this disk. Windows must be installed to a partition formatted as NTFS
Due to compatibility problems on file system, most versions of Windows operating system can be installed to partitions formatted to NTFS, and only few versions can be installed to a FAT partition. If the volume is formatted to an improper file system, you’ll receive error «Windows must be installed to a partition formatted as NTFS». Since the target partition has a file system issue, we can fix this error easily by changing its files system to NTFS.
Solution #1: Convert FAT file system to NTFS using Convert.exe
Converting the file system has the potential to result in data loss, and it is recommended to back up important data on the drive you are going to convert.
Step 1. Launch Command Prompt. Click Start button and enter cmd in searching box and press Enter.
Step 2. In the Command Prompt, type the following command convert G: /fs:ntfs and press Enter.
G is the drive letter of the partition that you want to change file system. You can open Windows Explorer to view the drive letter. Make sure the drive letter is correctly entered here. If it asks to enter the volume name, type in the name and press Enter.
Step 3. Convert.exe attempts to convert file system into NTFS and the process won’t take too long. After the conversion is complete, you might be prompted to restart your computer.
Solution #2: Format the partition into NTFS
Step 1. Copy the folder where DiskGenius installs to your bootable disk and then use the disk to boot computer.
Besides, you can create a bootable disk with DiskGenius: Click «Tools» menu and choose «Create WinPE Bootable USB Drive of DiskGenius» option.
Step 2. Launch DiskGenius, select the system partition you want to format to NTFS, and click «Format» button.
Step 3. Set the file system as NTFS and click Format button.
As to options like Cluster Size, Volume Label, Surface Scan, etc., you can follow the default value set by the partition manager.
Step 4. Click Yes from the message box which prompts all files on this partition will be lost after formatting.
Fix 5: Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure the disk’s controller is enabled in the computer’s BIOS menu
You may receive the warning message «This computer’s hardware may not support booting to his disk. Ensure the disk’s controller is enabled in the computer’s BIOS menu» when you try to install Windows. If you click Next to continue and you will receive another error «Windows cannot find a system volume that meets requirements for installation».
This error may indicate that BIOS settings of your computer are not properly configured, thus you can try setting BIOS to factory and go back to default settings. Plus, please ensure that your computer’s firmware (BIOS/UEFI) is up to date. Manufacturers often release updates that can improve compatibility and fix bugs.
Also, this issue is caused by improperly configured hard disk mode; in that case, you need to change AHCI to Compatibility in BIOS. If there is not Compatibility option, you can select IDE. Additionally, if your system uses RAID, ensure that the RAID configuration is set up correctly in the BIOS/UEFI settings.
Fix 6: Windows cannot be installed to this disk. The disk may fail soon. If other hard disks are available, install Windows in another location
There might be something wrong with the hard drive if you get the error «Windows cannot be installed to this disk. The disk may fail soon. If other hard disks are available, install Windows in another location.» You should be cautious if the hard drive is damaged, as data on that disk may get lost, which is similar to the system warning
Windows detected a hard disk problem
, you should have a check for hard drive health condition.
Step 1. Check hard drive or SSD health via accessing S.M.A.R.T. data.
Select the hard disk that may fail soon and click Disk menu to choose View S.M.A.R.T. Information. If the health status is NOT Good, then backup data and verify bad sectors following Step 2.
Step 2. Check bad sectors for the hard drive in questions.
Still in DiskGenius, select the disk you want to check bad sectors, click «Disk» and choose «Verify Or Repair Bad Sectors«. Then click Start Verify button to start scanning sectors for selected area.
If the hard disk contains bad sectors, you can try repairing it with DiskGenius. However, it is crucial to backup all files before proceeding the repairing, as the process of repairing bad sectors can result in data loss. It is important to note that certain bad sectors caused by physical damages may be irreparable. In that situation, you can manually create a hidden partition on that area to isolate bad sectors. Moreover, it is recommended to install Windows operating system on a health hard drive or SSD that does not have bad sectors.
Fix 7: Windows is unable to install to the selected location. Error: 0x80300001
While installing Windows 7, you might run into an error saying «Windows is unable to install to the selected location. Error: 0x80300001». This error typically occurs when you are asked to exchange hard drives in order to install required drivers on the system and the system disk hasn’t been put back. It can also be caused by other reasons, so you may have to try more than one solution to solve it.
Solution #1: Reconnect Windows installation disk
Step 1. Boot computer using a Windows installation CD or USB disk to access the setup wizard. Go to the step which requires selecting a partition and click «Load Driver». When you see the error message, ignore it.
Step 2. Reinsert the installation disk and click Refresh link and then Advanced Drive Options to create a new partition with any size. If Windows prompts it has to carry out some operations, click «OK». Then you can see a new system partition and a new primary partition.
Step 3. Select the new primary partition and click «Next» button. Then the setup should continue without any errors.
Solution #2: Change boot order
It’s possible that this error occurs when the disk is not set as the boot disk provided that you are not using RAID. In that circumstance, you can get rid of the problem by changing boot order in BIOS.
Step 1. Enter BIOS Setup Utility. Turn on or restart your computer and watch message appearing on screen. A specific key such as Del or F2 will be promoted on the screen to enter BIOS. Press that key.
Step 2. Select the «Boot» tab. All BIOS utilities look different, but boot option is definitely included. Locate and select it.
Step 3. Set the hard drive where you want to install system as the boot device. Any attached storage devices like external hard drives, USB flash drives, floppy drives, etc. are listed here too, and you can change their order manually. Save changes and exit.
Fix 8: Windows cannot be installed to Disk 0 Partition 1
People who try to install Windows using internal SAS controllers for hard drives will encounter the message «Windows cannot be installed to disk # partition #». Usually this issue occurs due to SAS driver issues or corrupted $MFT. The Microsoft Windows partition manager is out of touch with drivers after changes were made on partitions. Here is an approach to troubleshoot the problem.
Step 1. When the Windows installation process asks where you want to install Windows, load the SAS driver from a USB key. If the disk is larger than 2TB and needs to be converted to GPT, you can follow steps in previous solutions to do the conversion.
Step 2. View and check all possible partitions available for system installing. If the disk does not show up, have a check whether the drive is correctly installed.
Step 3. Delete partitions until there is only unallocated Space on the disk. Click «New» and you can see recommended partition size. Continue «OK» and you can see 3 partitions: system partition, MSR partition and large partition.
For this step, you can also use DiskGenius to
repartition the hard disk
and choose GUID partition table, which is easier and intuitive.
Step 4. Select the big partition and click «Refresh». Then click «Next» to start the installation.
Conclusion
This guide addresses 8 scenarios that the «Windows cannot be installed to this disk» error appears during the Windows setup process. If the selected disk is of improper partition table style corresponding to BIOS settings, Windows installation will be blocked by errors. This article provides step by step solutions to each situation. If you have better solutions, please feel free to contact us or share with other readers. It is important to note that certain approaches mentioned in this article, such as disk formatting and partition deletion, may result in data loss. Therefore, it is essential to ensure that all files and partitions are backed up prior to executing these steps. The free partition manager DiskGenius provides proper and effective functions to help fix this error occurring in different cases, and it is a qualified partition and disk management tool as well as data recovery program for both beginners and professional users.