checking integrity of disk in Windows virtual machine

[hollistonma]

I'm running a Windows 10 virtual machine using Fusion 12.2.3 on a MBP running OS 12.4.   i use Windows primarily to run Quicken.  I received the following error message when using Quicken "Error accessing disk".  Quicken's help documentation says possible causes are disk errors or use of cloud storage.  Because I don't use cloud storage, I'm trying to see if the c: drive on the Windows VM has data integriy issues or bad sectors.

I've run "chkdsk /f /r" from the command prompt and found no errros/bad disks, etc.

Is there any other way to confirm whether the c: drive on the Windows VM contains any errors?  Could errors in the VM files cause this error?  if so, how can I check?  Thx in advance for the assistance.

[Technogeezer]

You may not use cloud storage, but by any chance are you using a Fusion shared folder to store your Quicken files. 

[hollistonma]

@Technogeezer,

No.  Quicken runs in Windows and my Quicken files are on the c: drive in Quicken.  I do store backups on a shared drive, however i haven't had to use a backup since 2018.

[continuum]

Check the vmware.log file - if Fusion reports very long timouts or corrupted vmdks youmay still be able to fix them

[hollistonma]

@continuum,

Thank you for the suggestion.  I'm not an IT expert so please bear with me.  Which log file(s) should I check and what should I be looking for?  i found the following log files in the Windows package:

mksSandbox-0.log

mksSandbox-1.log

mksSandbox-2.log

mksSandbox.log

vmware-0.log

vmware-1.log

vmware-2.log

vmware.log

Thx in advance for your assistance.

[continuum]

Read the one I mentioned. Search for "vmdk"

[hollistonma]

@continuum,,

Sorry about that...you were pretty clear!

Here are the entries I found when I searched for "vmdk":

2022-06-18T11:46:09.073Z In(05) vmx DICT scsi0:0.fileName = "Virtual Disk-000001.vmdk"
2022-06-18T11:46:09.718Z In(05) vmx DISK: OPEN scsi0:0 '/Users/Owner/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-000001.vmdk' persistent R[]
2022-06-18T11:46:09.739Z In(05) vmx DISK: Disk '/Users/Owner/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-000001.vmdk' has UUID '60 00 c2 94 34 9c 52 3b-db 76 e3 8c 7e 53 34 9d'
2022-06-18T11:46:09.739Z In(05) vmx DISK: OPEN '/Users/Owner/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-000001.vmdk' Geo (16317/255/63) BIOS Geo (16317/255/63)

Don't know how to interpret these entries so your assistance would be appreciated. 

I did find a number other entries at the beginning of the log file that indicated certain config files were not found or did not load.  For example:

2022-06-18T11:46:07.067Z In(05) vmx DictionaryLoad: Cannot open file "/Applications/VMware Fusion.app/Contents/Library/messages/en/vmware.vmsg": No such file or directory.
2022-06-18T11:46:07.069Z In(05) vmx DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2022-06-18T11:46:07.069Z In(05) vmx Msg_Reset:
2022-06-18T11:46:07.069Z In(05) vmx [msg.dictionary.load.openFailed] Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2022-06-18T11:46:07.069Z In(05) vmx ----------------------------------------
2022-06-18T11:46:07.069Z In(05) vmx ConfigDB: Failed to load /Library/Preferences/VMware Fusion/config

These are just a  few examples.  Should I be worried about these entries?

[continuum]

That looks good to me - damaged vmdks have an entry like "virtual disk needs repair"

Maybe run checkdsk /f /x /r C:
This will require a reboot and will launch after next boot.

[hollistonma]

@continuum,,

Thx for the quick replies!  Glad to know that the VM is good.  Have already run chkdsk and didn't find any errors.  Glad to rule out Fusion or Windows 10 causing the Qiuicken "error accessing disk" issue.

Looks like it may be a Quicken issue.  I've sent logs and sanitized file to them and will wait to hear back.

Appreciate your help as well as that of @Technogeezer .