4 Ways to Solve the Error Code 100006 on a Mac

Download and try Outbyte MacRepair right now to see what it can do for your Mac.

Developed for macOS

Recently, users have complained about getting the error code 100006 on their Macs. Well, it’s definitely not good news, especially that a lot of them seriously don’t have any idea on how to stop the error code from occurring. In an effort to ease the frustration on the part of users, we have created this article. We’ll try to discuss why a Mac is getting the error code 100006, what it is all about, and how to fix it.

What Is the Error Code 100006 on a Mac?

The error code 100006 on a Mac is usually an indication of a problem or issue with a specific Mac feature, program, or operation. It keeps on popping up on your screen, unless you take action to resolve it. To be able to get around it, you have to find out what is causing the error code to show up.

The Common Causes of the Mac Error Code 100006

Your Mac often performs a number of processes and operations at once. This means we cannot directly attribute the error code to one certain issue or problem. But based on the reports and observations of Mac users who have come across the error code, we can conclude that the common causes could be any of the following:

• A Mac is infected by malware entities or viruses.
• There is no sufficient disk drive space.
• The improper uninstallation or removal of a file has triggered the error code to appear.
• Too many junk and unnecessary files have accumulated on the hard drive.

The Inconveniences That the Error Code 100006 Brings

Yes, the error code 10006 isn’t really good news for Mac users because it brings about many troubles and inconveniences, such as:

Pro Tip: Scan your Mac for performance issues, junk files, harmful apps, and security threats
that can cause system issues or slow performance.

• The error notification always appears when starting up or shutting down a Mac.
• Some programs, especially those that are associated with the error code, cannot open and run smoothly.
• Programs and apps cannot be installed or uninstalled properly.
• Some features and functions on a Mac cannot perform smoothly.

Other than the above inconveniences, the error code 100006 may also trigger other serious problems that may not be fixed with basic troubleshooting.

So, what should you do to resolve the 100006 error code and prevent it from appearing in the future?

How to Fix the Error Code 100006 on Your Mac

Below are some recommended fixes to the 100006 error code problem:

Fix #1: Scan Your Mac with a Reliable Cleaning Tool or App.

The majority of the error codes you may encounter on your Mac are mostly caused by malware entities or virus infections. They attack and destroy different settings, files, and configurations you have on your Mac, resulting in corrupted or invalid features.

The good news is that Apple has already installed invisible background protections on your Mac: File Quarantine/Gatekeeper and Xprotect. However, the latest strain of viruses might go undetected by these apps.

If you suspect that the error code is showing on your Mac due to a virus infection, it is recommended that you perform a quick scan on your Mac. Use any reliable antivirus program to delete any viruses and threats that are present on your Mac.

Here’s a handy tip: Before starting a system scan, make sure that you have already updated your virus database. Otherwise, you won’t be successful with your virus removal.

FIX #2: Clean Up Your Mac.

In general, the programs you install on your Mac would need a particular file for them to run. When your Mac detects duplicates of such files, it will be confused. If this happens, error codes, such as the error code 100006, could be triggered. This is why it is important to clean up your Mac to get rid of duplicate and unnecessary files .

Sure, you can manually check and find duplicate files on your Mac. However, it is not recommended as it will take much of your time. Instead, it is advised to scan and clean your Mac with a reliable cleaning tool like Outbyte MacRepair. In just a few clicks, it can locate, identify, and clean up all the unnecessary files on your Mac.

Fix #3: Uninstall Any Problematic App.

With all the new trending apps out there, one would be quickly enticed to have them installed on their computers. They don’t realize that problems will come out when a lot of apps have been installed.

Once problematic apps or programs are successfully installed on a Mac, they will significantly affect the overall performance of other apps, programs, or even your system’s features. They can also trigger the error code 100006 to show. In this case, you really have to thoroughly check all the programs and apps installed on your Mac.

To uninstall a program that you suspect is problematic, follow these steps:

1. Go to Finder.
2. Select Applications.
3. Find the icon of the program that you want to uninstall.
4. Drag it to Trash.
5. Finally, right-click on Trash and select Empty Trash.

If uninstalling problematic apps is too challenging for you, fret not because you can count on professional tools to do the job. You can do a quick search on Google to get a list of the best uninstall programs or apps for Mac.

Fix #4: Manage Your Disk Usage.

With insufficient disk space, it is impossible for your Mac to perform smoothly and effectively. In some cases, it also causes the error code 100006 to appear. So, if your hard disk space is running low, take the time to free up space. Do not let any unnecessary files and data take up your storage space.

You can always start by manually checking your disk to find out what files are taking up space. Use a hard disk analysis program to scan your Mac’s hard disk and identify what folders are consuming most of your storage space. From there, you can start deleting the space hogs and freeing up valuable space.

If you still need the files, you might want to transfer them to other storage media. Just make sure you don’t delete any important system files.

Wrapping Up

It is true that error codes on Macs are inevitable. They show up when you least expect them. However, if you only take care of your Mac and use it the right way, you can prevent any problem from surfacing. Perform regular scans, delete unnecessary files, and manage your disk space.

Do you know other ways to fix the error code 10006 on a Mac? Share them with us in the comments!

If you’re running into errors and your system is suspiciously slow, your computer needs some maintenance work. Download Outbyte PC Repair for Windows, Outbyte Antivirus for Windows, or Outbyte MacRepair for macOS to resolve common computer performance issues. Fix computer troubles by downloading the compatible tool for your device.
See more information about Outbyte and uninstall instructions . Please review EULA and Privacy Policy .

DiskMaker X

Basically, there is something in the pathname of your macOS Install app that DiskMaker X does not like, and most of the time the issue is parenthesis because you renamed the app or included it in a folder that has the version or build number between parenthesis, i. e. (18F132). Parenthesis are difficult to deal with when integrating shell script code in AppleScript, so the best way to avoid this bug at this time is to just remove the parenthesis from the path of the app.

Where can I get a previous macOS Install app ?

Charles Edge nicely compiled the list of download links for previous versions of macOS installer apps. Beware that some of these versions must be purchased (basically, all macOS versions before 10.9).

When using DiskMaker X 7 for High Sierra, I encounter this error message : “The disk could not be created because of an error: An error occured: -10006. Finder got an error: Can’t set alias \”Install macOS High Sierra:Install macOS High Sierra. app\” to <425, 76>.”

When using DiskMaker X 8 for Mojave, I encounter this error message : “The disk could not be created because of an error: An error occured: -10006. Finder got an error: Can’t set alias \”Install macOS Mojave:Install macOS Mojave. app\” to <425, 76>.”

First, please update to DiskMaker X 7.0.1 or DiskMaker X 8.0.1. It should fix this bug and some.
Second, it may happen that your macOS Install app (either High Sierra or Mojave) is not complete. Check its size : if the installer is about 20 MB large, it’s a stub which can’t be used with DiskMaker X. You need the FULL installer. To be sure to download the full macOS installer, have a look here for macOS High Sierra or here for macOS Mojave. The idea is to use an app that will force download of the full macOS install app.

I plan to add a feature to check the size of the installer before trying to build an install disk in the not-too-distant future.

When creating the Install disk with DiskMaker X, I encounter this error message : “The disk could not be created because of an error: An error occured: -10006.”

This happens sometimes when creating the install disk because a false mount is created as some point. Basically, a false mount is a folder created with the same name as your Install drive, and that makes the Install disk adopt the same name with “1” at the end, i. e. “Install Mac OS Sierra 1”.

If this error happens:

• in Finder, click on Go > Go to Folder menu ;
• Type /Volumes/
• If a folder (not a disk !) is named “Install macOS Sierra”, “Install OS X Yosemite”, or “Install OS X El Capitan”, delete the folder (you may need admin rights, thus type your admin name and password).
• Reboot your Mac
• Try again.

That should do it. I will try to fix it in a future version (if I manage to get why this happens sometimes in some configurations…

“This copy of the Install OS X [OS X Name] application can’t be verified. It may have been corrupted or tampered with during downloading.”

Due to an expiration of OS X App Store certificates, installers of OS X downloaded prior to February 14th of 2016 can’t be used to re-install OS X without encoutering this error. This is not a problem with DiskMaker X per se, but with the installers provided by Apple.

I encounter this message:

“This copy of the Install OS X [OS X Name] application can’t be verified. It may have been corrupted or tampered with during downloading.”

Due to an expiration of OS X App Store certificates, installers of OS X downloaded prior to February 14th of 2016 can’t be used to re-install OS X without encoutering this error. This is not a problem with DiskMaker X per se, but with the installers provided by Apple.

There are three ways to avoid this problem :

• If you did not erase your Mac and its OS is still working fine, reboot on its hard drive, open System Preferences > Date and Time, uncheck Automatically set up date and time and set the date 13th of February 2016, then disconnect from network and reboot;
• If you don’t have an OS installed anymore, reboot on your OS X install disk built with DiskMaker X, open Terminal and type:

Which will set the date and time on the 10th of October 2015 at 10:10 (it’s just easier for me to remember, but any date in the five last years or so should work).

The last solution (and the best) is to re-download the OS X installers from the App Store. Which is OK for El Capitan if you currently run it, but what if you want to re-download older OS? Sadly, Apple does not allow to re-download say, Lion or Mountain Lion, if your Mac already runs a more recent version of OS X (which sucks REALLY badly). There are two solutions here :

• Re-install at least Lion on a drive, boot on it, open App Store and re-download the apps…
• If your Mac does not support older versions of OS X to reboot on, use a virtual machine with Parallels Desktop or VMWare Fusion to re-install Lion in it, then re-download the installers from Lion’s App Store.

Also, beware that if you have OS X installers on any volume mounted on your Mac: the first copy of the installer the App Store will find will be updated if you decide to download a new version, wherever this copy of the installer is on your boot drive or not.

I bought a recent Mac, I built a disk with DiskMaker X but I can’t boot on it !

This one is tricky to explain. Please take a drink first.

When a new model of Mac is available, it usually ships with an “almost” standard version of OS X. I wrote “almost” as it is a special build of OS X, designed only for this specific kind of new Mac.

The problem is quite well explained here:

The following points are especially important:

1. Some Macs may include a slightly later build version (but same numbered version) of Mac OS X on the Install or Restore discs than was preinstalled on your computer.
2. Do not use a Mac OS X version earlier than the one included with the computer.
3. Retail copies of Mac OS X may not always work properly with new Macs. Even if the retail version has been updated via Software Update to a later version of Mac OS X than originally came with a Mac, you may have unexpected issues. Always confirm operating system functionality by using the install disc that shipped with your particular Mac.

So ? If you get a new Mac, you won’t be able to use the installer downloaded from the App Store. The only solution to fully re-install your OS is to use OS X Internet Recovery.

However, there is also another way.

Basically: please be patient. When Apple will release a new version of OS X (say, 10.9.2), you will be able to download from the App Store the full OS X 10.9.2 installer which will provide a new “universal” build of OS X, allowing full install and allowing to build a new boot disk with DiskMaker X on your brand new Mac.

And please, wait before buying a new Mac the next time.

I stumble on a message: “An error occured: -2753. The variable OSX_App is not defined”

This happens if you use the 10.9.x DMG file instead of the full OS X Mavericks Installer app. It just won’t work. Please use the installer app.

When installing, I stumble on this error message: “This copy of the Install OS X Mavericks application can’t be verified. It may have been corrupted or tampered with during downloading.”

Known bug from Apple, your Mac’s clock is set to a wrong date/time. Check this KB article for a solution.

An error -1782 occurs after DiskMaker X copies files: “Can’t get disk “OS X Mountain Lion Install Disk” or similar.

Bug in version 3.0.1, corrected with 3.0.2 and later. The USB boot disk will work however.

An “Error -10660” happens in the building process.

Run DiskMaker X in an admin session (not a standard user session). It should work much better.

I built a disk with Lion DiskMaker 3.0 but can’t boot on it! It does not appear at startup or in the Startup disk Preference.

This has been fixed with DiskMaker X 3.0.1 and later. Give it a try. The (funny) explaination for this bug is here.

Can DiskMaker X build a drive with different versions of OS X ? Say, one partition with Lion Install, another one with Mountain Lion, and another one with Mavericks ?

Sure! Just format your removable drive with a few 8 GB partitions, and launch DiskMaker X. Then choose the “another kind of disk” option and select the right volume each time.

I can’t use DiskMaker X with Mac OS X 10.6.x if I try to use it with my Mavericks installer!

Because of a bug (or a feature?) in Apple’s built-in command createinstallmedia with 10.6.X, DiskMaker X is not compatible with versions of OS X prior to 10.7. I’m working on a fix, but it may take some time to make it available as it means using another completely different method. Check the blog regularly for updates.

I get an error: “The domain/default pair of (/Volumes/OS X Base System/System/Library/CoreServices/SystemVersion, Production Version) does not exist.”

This happens mostly because your OS X Install App is damaged. To check if this theory is correct :

1. Right-click or Ctrl+Cllick on the Installer OS X Mavericks application;
2. Go to Contents/SharedSupport;
3. Double-click InstallESD. dmg.

If an error message appears, you’ll have to download again the Installer app from the App Store. If it mounts properly, get in touch with me.

Note that Lion DiskMaker 3.0.1 should better handle this case.

I keep encountering an ASObjC Runner error (Error -43. File ASObjC Runner wasn’t found)!

This one is quite tricky. It’s a bug which happens randomly with Lion DiskMaker and has no real explaination, except some coding error.

The only way I found that could remove the problem would be to :

• Use Activity Monitor (in /Applicationsl/Utilities) to quit any instance of ASObjC Runner ;
• Reboot your Mac ;
• Check again if ASObjC Runner is still running in the Activity Monitor ;
• Then launch Lion DiskMaker again and try to build your disk.

Also sometimes, using a different, clean session may help.

If you have any insight in this problem, please get in touch with me.

After choosing the OS, Lion DiskMaker seems to hang.

This is related to some issues with Spotlight. To workaround this, open Terminal and type :

then type Enter key. Lion DiskMaker should resume automatically.

I am told I have no copy of OS X Install available.

The OS X Install application is automatically erased after you upgrade to the new version of OS X. If you need to download it again, open the Mac App Store, then open the Purchase page. You’ll be able to download Mac OS X Lion Install again.

The best time to use Lion DiskMaker is when you just finish downloading OS X from the Mac App Store. Create your disk with Lion Disk Maker , then install OS X.

I got my version of OS X pre-installed with my Mac. How can I get the OS X installer ?

There are two ways to do it.

– If you already purchased OS X on the Mac App Store (and therefore have a valid copy of OS X Install application), you can download the latest installer from Mac App Store first. This installer is compatible with Macs pre-equiped with your version of OS X.

– If you did not purchase OS X, but want to get an Install disc, there is a way to get the InstallESD. dmg file for your Mac. The method is not really easy though. Check Macworld for the full story. After you got the InstallESD. dmg file, use it to build your key or DVD with Lion DiskMaker.

I encountered the following message: The disk could not be created because of an error: An error occurred: 1. hdiutil: attach failed – No such file or directory

This happens if you chose the wrong Mac OS X Lion Install application, or if you mounted manually the InstallESD. dmg file first.

The simple answer is: don’t do this ? Lion DiskMaker is clever enough to detect your copy of OS X Install itself. Then it will mount the DMG file itself.

Yes, that’s cool, but I don’t have the complete OS X Install app and I just kept the InstallESD. dmg file. So do I have to re-download Lion again?

Don’t worry, if it does not find your OS X Install app, Lion DiskMaker will allow to select manually an InstallESD. dmg file.

Can I use a FireWire or SD-Card?

Yes, you can, though the USB drive has the advantage of being « universal » and works on any Mac.

My drive was completely erased!

DiskMaker X proposes two different ways to make a bootable disk:

– You can choose to use a dedicated 8 GB thumb drive ;

– Or you can choose a volume from any drive.

If you choose the 8 GB thumb drive option, the WHOLE disk will be erased. If you choose the second option, ONLY the dedicated volume will be erased, leaving any other volume on your disk intact.

However, if you chose the wrong option, Lion DiskMaker will list every volume that may be erased at the end of the process. Read slowly ?

And of course, backup any file on your drive before using the software if necessary. And use a dedicated, small drive (a 8 GB USB key is incredibly cheap these days).

Why did you remove the option to use a 4 GB USB Thumb drive?

The OS X install apps tend to be bigger and bigger with each new release. I used to remove some less essential package in the previous versions of Lion DiskMaker, but this could create some issues (many people complained that the installer then failed when installing OS X).

Also, the price of 8 GB USB thumb stick drives fell , as you can get an 8 GB drive for less than $7 now. So please do yourself a favor, and get one. This drive should be « future-proof » (until Apple makes OS X installer larger than 8 GB…).

Can I redistribute this software ?

Sure, as long as you mention the author and don’t suppress any comment or change anything in its package.

Booting from the DVD is slooooow as hell…

A DVD will always be slower than a USB key, and it seems Lion’s disk image is not optimized for use with optical disks. Avoid it, and use a USB key.

Why did you not rename Lion Diskmaker now that Mountain Lion is available ?

Well, I like this name better than « OS X Diskmaker ». That’s it.

(also: « Lion Diskmaker » should make Apple’s lawyers go less ballistic than « OS X Diskmaker ».