'OSX update cannot be installed on this disk does not meet requirements' I have gone to disk utility and checked and repaired the permissions and even ran disk verify all is OK. The drive has one partition which I named the same as the last HDD 'Macintosh HD' it has 1.7 TB available space showing with the root directory '/' at the top of the. It comes from checks made when the installer loads the package, & means that installer thinks some aspect of those checks means that the volume is unsuitable. It might be that a plist file or version string within one, is missing or altered so as not to be recognised, or that systemversion says it's a server; or most anything that is looked at.
Applies to
Summary
MBR2GPT.EXE converts a disk from the Master Boot Record (MBR) to the GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. The tool is designed to be run from a Windows Preinstallation Environment (Windows PE) command prompt, but can also be run from the full Windows 10 operating system (OS) by using the /allowFullOS option.
MBR2GPT.EXE is located in the WindowsSystem32 directory on a computer running Windows 10 version 1703 (also known as the Creator's Update) or later.The tool is available in both the full OS environment and Windows PE. To use this tool in a deployment task sequence with Configuration Manager or Microsoft Deployment Toolkit (MDT), you must first update the Windows PE image (winpe.wim, boot.wim) with the Windows ADK 1703, or a later version.
See the following video for a detailed description and demonstration of MBR2GPT.
You can use MBR2GPT to:
Offline conversion of system disks with earlier versions of Windows installed, such as Windows 7, 8, or 8.1 are not officially supported. The recommended method to convert these disks is to upgrade the operating system to Windows 10 first, then perform the MBR to GPT conversion.
Important
![]()
After the disk has been converted to GPT partition style, the firmware must be reconfigured to boot in UEFI mode.
Make sure that your device supports UEFI before attempting to convert the disk. Disk Prerequisites
Before any change to the disk is made, MBR2GPT validates the layout and geometry of the selected disk to ensure that:
If any of these checks fails, the conversion will not proceed and an error will be returned.
Syntax
Options
ExamplesValidation example
In the following example, disk 0 is validated for conversion. Errors and warnings are logged to the default location, %windir%.
Conversion example
In the following example:
As noted in the output from the MBR2GPT tool, you must make changes to the computer firmware so that the new EFI system partition will boot properly.
SpecificationsDisk conversion workflow
The following steps illustrate high-level phases of the MBR-to-GPT conversion process:
Creating an EFI system partition
For Windows to remain bootable after the conversion, an EFI system partition (ESP) must be in place. MBR2GPT creates the ESP using the following rules:
If the existing MBR system partition is not reused for the ESP, it is no longer used by the boot process after the conversion. Other partitions are not modified.
Important
If the existing MBR system partition is not reused for the ESP, it might be assigned a drive letter. If you do not wish to use this small partition, you must manually hide the drive letter.
Partition type mapping and partition attributes
Since GPT partitions use a different set of type IDs than MBR partitions, each partition on the converted disk must be assigned a new type ID. The partition type mapping follows these rules:
In addition to applying the correct partition types, partitions of type PARTITION_MSFT_RECOVERY_GUID also have the following GPT attributes set:
For more information about partition types, see:
Persisting drive letter assignments
The conversion tool will attempt to remap all drive letter assignment information contained in the registry that correspond to the volumes of the converted disk. If a drive letter assignment cannot be restored, an error will be displayed at the console and in the log, so that you can manually perform the correct assignment of the drive letter. Important: this code runs after the layout conversion has taken place, so the operation cannot be undone at this stage.
The conversion tool will obtain volume unique ID data before and after the layout conversion, organizing this information into a lookup table. It will then iterate through all the entries in HKLMSYSTEMMountedDevices, and for each entry do the following:
Troubleshooting
The tool will display status information in its output. Both validation and conversion are clear if any errors are encountered. For example, if one or more partitions do not translate properly, this is displayed and the conversion not performed. To view more detail about any errors that are encountered, see the associated log files.
Logs
Four log files are created by the MBR2GPT tool:
![]()
These files contain errors and warnings encountered during disk validation and conversion. Information in these files can be helpful in diagnosing problems with the tool. The setupact.log and setuperr.log files will have the most detailed information about disk layouts, processes, and other information pertaining to disk validation and conversion. Note: The setupact*.log files are different than the Windows Setup files that are found in the %Windir%Panther directory.
The default location for all these log files in Windows PE is %windir%.
Interactive help
To view a list of options available when using the tool, type mbr2gpt /?
The following text is displayed:
Return codes
MBR2GPT has the following associated return codes:
Determining the partition type
You can type the following command at a Windows PowerShell prompt to display the disk number and partition type. Example output is also shown:
You can also view the partition type of a disk by opening the Disk Management tool, right-clicking the disk number, clicking Properties, and then clicking the Volumes tab. See the following example:
If Windows PowerShell and Disk Management are not available, such as when you are using Windows PE, you can determine the partition type at a command prompt with the DiskPart tool. To determine the partition style from a command line, type diskpart and then type list disk. See the following example:
In this example, Disk 0 is formatted with the MBR partition style, and Disk 1 is formatted using GPT.
Known issueMBR2GPT.exe cannot run in Windows PEVolume Does Not Meet The Requirements For Os X Update Download
When you start a Windows 10, version 1903-based computer in the Windows Preinstallation Environment (Windows PE), you encounter the following issues:
Issue 1 When you run the MBR2GPT.exe command, the process exits without converting the drive.
Issue 2 When you manually run the MBR2GPT.exe command in a Command Prompt window, there is no output from the tool.
Issue 3 When MBR2GPT.exe runs inside an imaging process such as a Microsoft Endpoint Configuration Manager task sequence, an MDT task sequence, or by using a script, you receive the following exit code: 0xC0000135/3221225781.
Cause
This issue occurs because in Windows 10, version 1903 and later versions, MBR2GPT.exe requires access to the ReAgent.dll file. However, this dll file and its associated libraries are currently not included in the Windows PE boot image for Windows 10, version 1903 and later.
Workaround
To fix this issue, mount the Windows PE image (WIM), copy the missing file from the Windows 10, version 1903 Assessment and Development Kit (ADK) source, and then commit the changes to the WIM. To do this, follow these steps:
Volume Does Not Meet The Requirements For Os X Update Can T Be Installed On This DiskRelated topicsVolume Does Not Meet The Requirements For Os X Update El Capitan
Windows 10 Enterprise system requirements
Windows 10 Specifications Windows 10 IT pro forums Volume Does Not Meet The Requirements For Os X Update 2017
When I downloaded a upgrade package from Apple (http://www.apple.com/se/downloads/) for the Mac OS X v10.6.2 Update, it failed to install on my hard drive.
The installation program says: 'Mac OS X Update Combined can't be installed on this disk. This volume does not meet the requirements for this update.' According to the Disk Utility, the Partition Map Scheme is GUID Partition Table. Some people have listed this as a requirement What is the real reason for the failure? Perhaps there is some clue in /var/log/install.log. Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: @(#)PROGRAM:Install PROJECT:Install-562 Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: @(#)PROGRAM:Installer PROJECT:Installer-429 Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Hardware: MacBookPro5,1 @ 2.53 GHz (x 2), 4096 MB RAM Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Running OS Build: Mac OS X 10.6 (10A380) Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: TMPDIR=/var/folders/N7/N7JdEuojGimnQsNTkq0nK++++TI/-Tmp-/ Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: SHELL=/bin/bash Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: HOME=/Users/macbook Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: USER=macbook Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: LOGNAME=macbook Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: DISPLAY=/tmp/launch-wIQnbn/:0 Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: SSH_AUTH_SOCK=/tmp/launch-G6NiRi/Listeners Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: Apple_PubSub_Socket_Render=/tmp/launch-pgW8jq/Render Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: COMMAND_MODE=unix2003 Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Env: __CF_USER_TEXT_ENCODING=0x1F5:0:0 Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Mac OS X Update Combined Installation Log Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Opened from: /Volumes/Mac OS X 10.6.2 Update Combo/MacOSXUpdCombo10.6.2.pkg Apr 8 17:07:19 Macbooks-MacBook-Pro-2 Installer[2922]: Package Authoring Warning: Package reference does not include required hash for package id auto. I also tried to install the Mac OS X 10.6.1 Update. The log in /var/log/install.log was: Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: @(#)PROGRAM:Install PROJECT:Install-562 Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: @(#)PROGRAM:Installer PROJECT:Installer-429 Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Hardware: MacBookPro5,1 @ 2.53 GHz (x 2), 4096 MB RAM Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Running OS Build: Mac OS X 10.6 (10A380) Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: TMPDIR=/var/folders/XK/XK3cnUTIHWuKThVnxatybU+++TM/-Tmp-/ Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: SHELL=/bin/bash Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: HOME=/Users/helge Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: USER=helge Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: LOGNAME=helge Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: DISPLAY=/tmp/launch-7KVwpc/:0 Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: SSH_AUTH_SOCK=/tmp/launch-4HaAHR/Listeners Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: Apple_PubSub_Socket_Render=/tmp/launch-4avL87/Render Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: COMMAND_MODE=unix2003 Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Env: __CF_USER_TEXT_ENCODING=0x1F6:0:0 Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Mac OS X Update Installation Log Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Opened from: /Volumes/Mac OS X 10.6.1 Update/MacOSXUpd10.6.1.pkg Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Package Authoring Warning: Package reference does not include required hash for package id patch. Apr 8 23:13:23 Macbooks-MacBook-Pro-2 Installer[3501]: Package Authoring Warning: Package reference does not include required hash for package id auto. I bought the computer used. Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |