2 Replies Latest reply on Sep 11, 2019 5:13 PM by TECH198

    VMWare Fuision issue with older OS's/Movaje ?

    TECH198 Enthusiast

      Has anyone seen this before ?

       

      Screen Shot 2019-08-13 at 8.50.45 am.png

      In VMWare Fusion 11.1.1, when creating old installers of OS X (Mavericks, Yosemite El Captitan), sometimes you get the above in Finder .. Two instances of your own internal hard drive/SSD even they both point to the same.

       

      This only happens when installing creating new installs and can be reproduced all the time when gong to File >> New and walking through the wizard. When it comes to selecting the image, if you select app bundle prior to Mojave you  the above.

       

      In all cases, after creating, when you relauch the same VM, sometimes if the issue  produced as well,  lesser fror Safe boot, and usually booting *into* safe boot and back to normal, 'temporarily resolves issue.

       

      I thought it was something to do at first with old Apple installers and Mojave, but since it only happens with VMWare Fusion, it could just be Fusion incompatible with older OS'S or something// References to application references in Mac.

       

      Can anyone else reproduce this if they have old installers lying around? in some case's "Remove from sidebar" on right click doesn't work either under VM is deleted.

       

      Repaired Disk Permissions, an issue persists.

       

      Running 10.14.6 on host.

        • 1. Re: VMWare Fuision issue with older OS's/Movaje ?
          dlhotka Virtuoso

          That's a bug in OSX itself, I find it when I'm mounting volumes without using Fusion.

           

          ---------------------------------------------------------------------------------------------------------

          Was it helpful? Let us know by completing this short survey here.

           

           

          • 2. Re: VMWare Fuision issue with older OS's/Movaje ?
            TECH198 Enthusiast

            I think that is incorrect... Because fr me it only happens when using Fusion.. The fact its not running perhaps could be a service fusion uses, but there is no doubt it must be a fusion issue..

             

            Evidence of this topped again, after the Apple supplemental update, but this time it's stranger:

             

            Screen Shot 2019-09-12 at 7.54.00 am.png

             

            Its not the temporary image at that is saved within the package..

             

            My bases for all this happening, is when fusion is used, (...or at least installed), but for me... i only ever see these things when installing an MacOS within VMWare Fusion..

             

            How else you you explain these only crop up only after Vmware Fusion in on the system ?

            I've looked in Console for evidence but can't find a thing that would put it down to this as being an OS issue

             

            I'm tempted to do another clean install on the host, but this time go 24 hours "without" installing Fusion, just to see.... In all cases, these problems happen (different i admit), but still problems after installing the app.

             

            Apple just push me into VMWare as the cause .