Frank Nitty Posted October 12, 2017 Share Posted October 12, 2017 I got the following error "The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" after creating my USB installer and booting into and now stomped at what to do next. I have already copied the apfs.efi file to EFI/CLOVER/drivers64UEFI. I'm having the issue with rig #1 in my sig. Any help referring me to the right direction would be greatly appreciated. Link to comment Share on other sites More sharing options...
Jarods Posted October 12, 2017 Share Posted October 12, 2017 For me was. 1 Disable integrated graphics card. 2 Replace the file FakeSMC.kext with the most current version in the Other folder and update with the application Kext Utility This works for me. Link to comment Share on other sites More sharing options...
Frank Nitty Posted October 13, 2017 Author Share Posted October 13, 2017 I still can't figure out why it won't pass that error page on the installer. Any other ideas would be greatly appreciated. Link to comment Share on other sites More sharing options...
andrew.j.aguirre Posted October 14, 2017 Share Posted October 14, 2017 I am getting the same error. I have tried using a later version of FakeSMC.kext, disabling graphics card, and re downloading the installer several times. Nothing seems to get past that error. Link to comment Share on other sites More sharing options...
Autines Posted October 14, 2017 Share Posted October 14, 2017 I still can't figure out why it won't pass that error page on the installer. Any other ideas would be greatly appreciated. I am getting the same error. I have tried using a later version of FakeSMC.kext, disabling graphics card, and re downloading the installer several times. Nothing seems to get past that error. Just try to delete emufivariable in clover. Link to comment Share on other sites More sharing options...
fusion71au Posted October 14, 2017 Share Posted October 14, 2017 I got the following error "The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" after creating my USB installer and booting into and now stomped at what to do next. How did you create your USB installer? The old "restore BaseSystem.dmg method" needs modification in High Sierra to avoid the OSInstall.mpkg error when booting the installer - see post#13 & post#15. Apple approved installation methods for High Serra are "createinstallmedia" for USB installer and "startosinstall" to deploy directly on hard drive/SSD. If you see the error rebooting into "macOS Install" (after "/macOS Install Data" folder is created on the target partition), then it maybe due to incorrect FakeSMC keys in your NVRAM or outdated Firmware data in SMBIOS - try all actions below together: Delete EmuVariableUefi-64 (for UEFI systems) or NVRAM.plist files from all EFI partitions, incl USB installer (for legacy BIOS systems). I also run the terminal command sudo NVRAM -c to reset my NVRAM before installing/upgrading High Sierra. Try Clover r4220+ and remove FirmwareFeatures/FirmwareFeaturesMask/PlatformFeature and BIOS version/release date/Board-ID data from config.plist/SMBIOS to allow Clover to inject up to date values. Update to @Slice's latest FakeSMC v3.50. Erase your target volume with Disk Utility then re-run "Install macOS High Sierra.app". Some background on "OSInstall.mpkg error" in post#3104. 5 Link to comment Share on other sites More sharing options...
andrew.j.aguirre Posted October 15, 2017 Share Posted October 15, 2017 run the terminal command sudo NVRAM -c to reset my NVRAM before installing/upgrading High Sierra. Try Clover r4220+ and remove FirmwareFeatures/FirmwareFeaturesMask/PlatformFeature and BIOS version/release date/Board-ID data from config.plist/SMBIOS to allow Clover to inject up to date values. Update to @Slice's latest FakeSMC v3.50. Thank you! I double checked to do all of these things, and although I did use an updated version of FakeSMC, I did copy and replace with the one you linked to, just in case. It worked! I was able to upgrade to High Sierra on my machine. Thank you very much! 1 Link to comment Share on other sites More sharing options...
Frank Nitty Posted October 16, 2017 Author Share Posted October 16, 2017 How did you create your USB installer? The old "restore BaseSystem.dmg method" needs modification in High Sierra to avoid the OSInstall.mpkg error when booting the installer - see post#13 & post#15. Apple approved installation methods for High Serra are "createinstallmedia" for USB installer and "startosinstall" to deploy directly on hard drive/SSD. If you see the error rebooting into "macOS Install" (after "/macOS Install Data" folder is created on the target partition), then it maybe due to incorrect FakeSMC keys in your NVRAM or outdated Firmware data in SMBIOS - try all actions below together: Delete EmuVariableUefi-64 (for UEFI systems) or NVRAM.plist files from all EFI partitions, incl USB installer (for legacy BIOS systems). I also run the terminal command sudo NVRAM -c to reset my NVRAM before installing/upgrading High Sierra. Try Clover r4220+ and remove FirmwareFeatures/FirmwareFeaturesMask/PlatformFeature and BIOS version/release date/Board-ID data from config.plist/SMBIOS to allow Clover to inject up to date values. Update to @Slice's latest FakeSMC v3.50. Erase your target volume with Disk Utility then re-run "Install macOS High Sierra.app". Some background on "OSInstall.mpkg error" in post#3104. Your following solution from another page was what did the trick: @XCiLNZ, The problem is this step: "Copied the real Packages folder from InstallESD.dmg to USB/System/Installation/ " doesn't work in High Sierra anymore and will cause the OSInstall.mpkg error. All that is required to make a working USB installer is to expand BaseSystem.dmg, replace the "Install macOS High Sierra.app" on the root of the USB with the full version (>5GB), then place your kernel in /System/Library/Kernels+your usual changes to /S/L/E (remove AppleTyMCEDriver.kext etc). ..... Didn't realize the Packages step was no longer valid in creating a bootable USB. Thanks, I owe you one. 2 Link to comment Share on other sites More sharing options...
G.com Posted October 24, 2017 Share Posted October 24, 2017 Hi Guys, above seems a bit crucial to me. All I did, and it worked three times was the following: - Make USB Installer - Boot from USB - Run Installer - before second boot start working System - In there go to "Macintosh HD" or what ever you call your new Installation, go into Installation folder, show package content of ESDInstall.pkg - Copy "Package" to Installation Folder - Within Installation folder create ../System/Installation/ and copy Package Folder in here as well - Copy "OSXInstall.mpkg" to Installation Folder - finally copy all above to root folder of "Macintosh HD" --- - Install Clover to EFI of "Macintosh HD" - use SMBIOS 14,2 --- - last but not least unplug all other HD´s and run the second Installation Boot --- It is not mandatory using the 14,2 but this said it avoids a lot of other hick ups I had. It worked 100% for me. Link to comment Share on other sites More sharing options...
dss862 Posted November 1, 2017 Share Posted November 1, 2017 Please help i cannot proceed to 2nd part high sierra installation osinstall.mpkg is either missing or damaged ...i am using dell 7559 uhd laptop Link to comment Share on other sites More sharing options...
G.com Posted November 1, 2017 Share Posted November 1, 2017 Hi Jeff, as mentioned above I had the very same issue. Do you have a running system? Then do as I suggest copy the files all over the installation HDD. This will make it work! Otherwise, try deleting EmuVariableUefi-64 which in my case is and has always been in the driver folder. To what I discovered for me the major driving factor is a clean SMBIOS declaration with SMUUID, ROM and all other data. Since I have that I can re-install from scratch without any issue. As you are making a HackbookPro - I am out in detail, I use original hardware for that purpose I only like the challenge to build a nice desktop. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 2, 2017 Share Posted November 2, 2017 Seeing this too when attempting the update from 10.13 to 10.13.1 and no matter what I do (unplug all other drives, clear nvram, remove EmuVariableUefi-64, clear FirmwareFeatures/FirmwareFeaturesMask/PlatformFeature/BIOS Version/Release Date/Board-ID/etc. Clover SMBIOS, redo those SMBIOS Clover settings, redownload the actual update, do a clean Clover install with default settings, update all kexts, remove all kexts except Slice's FakeSMC, etc.) it doesn't work. I have a feeling re-downloading the full 5.2 GB High Sierra install and reinstalling macOS would work (since that's what I had to do a month ago when the supplemental update came out because this SAME thing happened), but that's too much of a PITA to deal with when there's an update and I don't have a very fast connection to begin with to keep redownloading and recreating my install USB drive with every little update. Any other ideas to get this actually working? High Sierra has been a total pain since day one, IMO. Link to comment Share on other sites More sharing options...
G.com Posted November 2, 2017 Share Posted November 2, 2017 Hi Awsome, check the installation OS Folder. Show package content for installer and copy package folder as discribed above. Shall work. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 2, 2017 Share Posted November 2, 2017 Where's the installation OS folder? From the installer USB? Does it work if you use an older 10.13? Do you reinstall (hence the second boot)? Is it possible you can post screenshots for a tutorial? I'll give it a go! Thanks! Link to comment Share on other sites More sharing options...
Denicio Posted November 2, 2017 Share Posted November 2, 2017 I got the following error "The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" after creating my USB installer and booting into and now stomped at what to do next. I have already copied the apfs.efi file to EFI/CLOVER/drivers64UEFI. I'm having the issue with rig #1 in my sig. Any help referring me to the right direction would be greatly appreciated. Simple fix, put all your kexts on CLOVER/kexts/Other. It seems that the current 10.13.1 macOS version is does not fall under CLOVER/kexts/10.13 for some reason. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 2, 2017 Share Posted November 2, 2017 In my case all my kexts are already in the Other folder. I'm totally stumped. Link to comment Share on other sites More sharing options...
Denicio Posted November 2, 2017 Share Posted November 2, 2017 In my case all my kexts are already in the Other folder. I'm totally stumped. Which Clover version are you running? Also try to see on Clover Boot options which SMBIOS is autodetected for your system, might try something different for your case. Link to comment Share on other sites More sharing options...
G.com Posted November 2, 2017 Share Posted November 2, 2017 Hi Awsome, after the first installation run, you find an installation folder on your HDD. There you will find various files - sorry can't recap the real name. Something **install** >> show package content >> copy package folder to root folder under /Volumes/YourRootHDD/System/Installation/... and also the very same in your Installation folder. In addition I also copied the OSInstall.mpkg and the Package folder alone to both folders. I got sick to check which copy made the trick but 5 times I was able to overcome this. But most valuable answer - this will have made my USB to work - put all kext in "Others" and retry after Link to comment Share on other sites More sharing options...
psydrug Posted November 2, 2017 Share Posted November 2, 2017 Hello everyone For me also the problem appeared after I updated to macOSUpd10.13Supplemental update Update failed You can see the picture that appeared in the clover "Boot macOS Install from OS X" I have the problem there please help me Link to comment Share on other sites More sharing options...
dss862 Posted November 3, 2017 Share Posted November 3, 2017 Hi Jeff, as mentioned above I had the very same issue. Do you have a running system? Then do as I suggest copy the files all over the installation HDD. This will make it work! Otherwise, try deleting EmuVariableUefi-64 which in my case is and has always been in the driver folder. To what I discovered for me the major driving factor is a clean SMBIOS declaration with SMUUID, ROM and all other data. Since I have that I can re-install from scratch without any issue. As you are making a HackbookPro - I am out in detail, I use original hardware for that purpose I only like the challenge to build a nice desktop. i have no emuvariable .efi .. i noticed the date stamp during installation in verbose mode always stuck on oct 23,2017... i already reformat my usb and reinstall clover bootloader iand install high sierra app using createinstallmedia terminal..erase the installation disk thinking date stamp will change to current but the date always stuck on oct 23, 2017... is this has something to do with osinstall .mpkg is either missing or damaged Link to comment Share on other sites More sharing options...
Frank Nitty Posted November 3, 2017 Author Share Posted November 3, 2017 I've already successfully installed 10.3.0 (with the Supplemental Update included). You can refer to my guide I posted here as a resource. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted November 3, 2017 Share Posted November 3, 2017 Hi Awsome, after the first installation run, you find an installation folder on your HDD. There you will find various files - sorry can't recap the real name. Something **install** >> show package content >> copy package folder to root folder under /Volumes/YourRootHDD/System/Installation/... and also the very same in your Installation folder. In addition I also copied the OSInstall.mpkg and the Package folder alone to both folders. I got sick to check which copy made the trick but 5 times I was able to overcome this. But most valuable answer - this will have made my USB to work - put all kext in "Others" and retry after I "fixed" this by doing a clean install of 10.13 and doing an immediate update to 10.13.1 without installing any software first. But... I didn't have any Installation folder on my HD so instead I opened up the 10.13 Install macOS High Sierra app and extracted InstallESD.dmg (and its Package) and created the Installation folder under System and moved the Package contents there before upgrading 10.13 to 10.13.1. BTW, I already had all my kexts in the Other folder - I never used any in the 10.13 folder. Now the question is... will it successfully update from 10.13.1 to 10.13.2 once that's released or will it go through this exact same thing again? If this begins to become a PITA with every update, I may end up dropping macOS from my setup. Link to comment Share on other sites More sharing options...
G.com Posted November 3, 2017 Share Posted November 3, 2017 Yesterday, at least for me installing 10.13.1 it worked like a charm. Install, re-start, re-install Nvidia, Done! But funny enough my AppleID got blocked and I had to change password - what a small price to pay I had the same issue like you in the past but after first successful installation it never came back, wonder why. Link to comment Share on other sites More sharing options...
dss862 Posted November 3, 2017 Share Posted November 3, 2017 There is no way to access the installation folder on hdd if i stucked ok osintall.mpkg error..only resrart ...so i have to remove hdd from the laptop..using an external hdd case i have to do the editing on another computer and put it back to laptop for 2nd part installation.. Link to comment Share on other sites More sharing options...
Frank Nitty Posted November 8, 2017 Author Share Posted November 8, 2017 Just attempted to install 10.3.1 and it won't work and it's the 3rd time. Wtf Apple Link to comment Share on other sites More sharing options...
Recommended Posts