I installed an update and after that it won't boot again. There is no error message, the progress bar just stops and the screen goes back to the start screen.
i tried rebooting with "debug" but still there is not much to see.
There is a log file in the package, I scanned for "Fail" this is the result:
2019-05-21T17:07:49.361+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2019-05-21T17:07:49.361+01:00| vmx| I125: ConfigDB: Failed to load /Library/Preferences/VMware Fusion/config
2019-05-21T17:07:49.361+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/dev/null/Non-existing DEFAULT_LIBDIRECTORY/config": Not a directory.
2019-05-21T17:07:49.361+01:00| vmx| I125: ConfigDB: Failed to load /dev/null/Non-existing DEFAULT_LIBDIRECTORY/config
2019-05-21T17:07:49.361+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/dev/null/Non-existing DEFAULT_LIBDIRECTORY/settings": Not a directory.
2019-05-21T17:07:49.361+01:00| vmx| I125: ConfigDB: Failed to load /dev/null/Non-existing DEFAULT_LIBDIRECTORY/settings
2019-05-21T17:07:49.370+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Volumes/Data/Users/wvdheiden/Library/Preferences/VMware Fusion/config": No such file or directory.
2019-05-21T17:07:49.370+01:00| vmx| I125: ConfigDB: Failed to load ~/Library/Preferences/VMware Fusion/config
2019-05-21T17:07:49.389+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2019-05-21T17:07:49.389+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Applications/VMware Fusion.app/Contents/Library/settings": No such file or directory.
2019-05-21T17:07:49.389+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Applications/VMware Fusion.app/Contents/Library/config": No such file or directory.
2019-05-21T17:07:49.389+01:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "/Volumes/Data/Users/wvdheiden/Library/Preferences/VMware Fusion/config": No such file or directory.
2019-05-21T17:07:49.568+01:00| vmx| I125: MXUser TryAcquire failure probability = 0.000000
2019-05-21T17:07:50.002+01:00| vmx| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/isoimages_manifest.txt.sig failed: Could not find the file
2019-05-21T17:07:58.562+01:00| vmx| I125: deviceLock.tryLock.failProb debug failure probability = 0,000000
2019-05-21T17:07:58.563+01:00| vmx| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/isoimages_manifest.txt.sig failed: Could not find the file
2019-05-21T17:07:58.946+01:00| vmx| I125: DISKLIB-LIB_MISC : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.
2019-05-21T17:07:59.408+01:00| worker-429219| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/isoimages_manifest.txt.sig failed: Could not find the file
2019-05-21T17:07:59.409+01:00| worker-429219| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso.sha failed: Could not find the file
2019-05-21T17:07:59.409+01:00| worker-429219| I125: Failed to open Tools ISO image.
2019-05-21T17:07:59.409+01:00| worker-429219| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/isoimages_manifest.txt.sig failed: Could not find the file
2019-05-21T17:07:59.410+01:00| worker-429219| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso.sha failed: Could not find the file
2019-05-21T17:07:59.410+01:00| worker-429219| I125: Failed to open Tools ISO image.
2019-05-21T17:07:59.598+01:00| vmx| I125: ToolsISO: open of /Applications/VMware Fusion.app/Contents/Library/isoimages/isoimages_manifest.txt.sig failed: Could not find the file
Does not really makes sense to me.
Anybody who knows more?
Thanks
Walter
Please do not paste random snippets of the vmware.log - they dont help.
Attach the full vmware.log instead.