MP All Models DMG files keep remounting even after deletion

greg97

macrumors member
Original poster
Aug 22, 2012
49
7
Canada Eh?
When I mount a .dmg file or open certain other files on my drive, the Finder will automatically remount all .dmg images that I used previously. For example, I can mount DMG A, copy the application from within it to the Applications folder, then unmount it and delete it (and then empty trash). However, when I open DMG B or open files in my drive (no matter what type of file), the Finder will remount DMG A, so I have to unmount both DMG A and DMG B. This goes on and on with the same .dmg files for a while, until I've downloaded another set of .dmgs and opened them, then it will forget about the previous ones and keep repeating with the new ones.
I was hoping that with recently upgrading to Mojave, my Mac would have corrected this issue, but it's honestly been going on for years.
Any thoughts on how to solve this? Thanks!
 

MIKX

macrumors 65816
Dec 16, 2004
1,213
453
Japan
If you're using Mojave I had a similar problem after doing the 1st. full 6.05gb release of Mojave 10.14.6,

Preview and Quicktime Player would open files that I had opened from a week previously etc.

Apple released THREE final full 6.05 gb Mojave 10.14.6 installers.

I formatted a spare SSD to APFS and installed the 3rd. Mojave full installer - cloned that to an HFS_ Samsung 970 EVO M.2.

The problem is gone. Everything working swiftly & smoothly now.

I do not recommend using the Combo plus Supplemental upgrades - everything is in the current full download of 10.14.6 on the App Store.

1. Ensure tha tthere are no Mac OS installers in your Applicatons folder.

2. Go to the App Store search for " Mojave ".

3. When it pops up there should be a " GET " button in the top right of the screen - HIT that one.

5. Before installing COPY the installer somewhere to a folder titled " Mojave 3rd. full 6.05gb installer" for safekeeping and future re-installs.

Hope that helps.
 
  • Like
Reactions: greg97

greg97

macrumors member
Original poster
Aug 22, 2012
49
7
Canada Eh?
I'm not sure which version of the installers I have, it was the one I downloaded from the App Store a few weeks ago when I upgraded (in the way you just outlined). I did do a clean install of Mojave on my NVMe boot drive because I was using it for the first time.
Are you saying that because you cloned the install from your SSD to your NVMe, instead of installing it to the NVMe directly, is what solved your issue? Just curious why you did it that way instead? I'm assuming after install it changed the HFS to APFS on your NVMe, as from what I understand, that is the only way a mac will install any of the newer OS?
I'm thinking I've had this issue from at least High Sierra, but maybe before that as well, I can't remember, it's been a couple of years at least I've been putting up with it! :rolleyes:
 

MIKX

macrumors 65816
Dec 16, 2004
1,213
453
Japan
greg97

1. I installed the FULL 6.05 gb. Mojave 10.14.6 installer ( current App Store ) to an APFS formatted
internal SanDisk Ultra 3D SSD.

2. I CarbonCopy Cloned the above install to an HFS+ formatted Samsung 970 EVO M.2 blade.

3. I decided to completely re-install all of my often used Apps.

Finished.

========================================

Works without any issues whatsoever so far, in fact feels very smooth, quick in all aspects.

I prefer Mojave to High Sierra and much more preferred to Sierra.

=========================================

My mac-intuition tells me that the problems that people have been having with Mojave 10.14.6 have resulted from one or other of the following . . . .

1. Installing using the 10.14.6 Combo installer.

2. Installing from the very first full 10.14.6 installer ( was 6.04gb. current is 6.05gb )

3. either of the above plus the Supplemental installer.

I have always done FULL + FINAL + CLEAN installs to Mac OS / OSX new revisions eg : from Sierra to High Sierra and have very rarely had any serious issues except for Apple failings eg : In Sierra re-namimg Bluetooth devices didn't stick - this was fixed in High Sierra.
 
  • Like
Reactions: greg97