The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.
Microsoft and the Window logo are trademarks of Microsoft Corporation in the U.S. Alexa and all related logos are trademarks of, Inc. App Store is a service mark of Apple Inc. Mac, iPhone, iPad, Apple and the Apple logo are trademarks of Apple Inc., registered in the U.S. Android, Google Chrome, Google Play and the Google Play logo are trademarks of Google, LLC. Firefox is a trademark of Mozilla Foundation. or its affiliates in the United States and other countries. NortonLifeLock, the NortonLifeLock Logo, the Checkmark Logo, Norton, LifeLock, and the LockMan Logo are trademarks or registered trademarks of NortonLifeLock Inc.
LifeLock identity theft protection is not available in all countries.Ĭopyright © 2022 NortonLifeLock Inc. The Norton and LifeLock Brands are part of NortonLifeLock Inc. I checked the event log for chkdsk entries and there was nothing there listed so not sure what it fixed. I find it very strange that Nortons Auto-protect had to be disabled to fix what ever it fixed but I suppose it doesn't matter too much. Started the VM and it doesn't crash the host.guess this has fixed it? It took about 10mins and reached the final hurdle "Scanning and repairing drive (C:): 100% complete" and then, yep you guessed it stuck there for a few hours before I decided to again cut the power and reboot. So cut the power and rebooted but this time, the chkdsk I previously set before I did the memory diagnostic actually ran, woooohoooo off to a great start. I left the Windows Memory Diagnostic running yesterday and appeared stuck on 88% - a common 'problem' according to the internet where it looks like it is not doing anything but in fact can take hours to complete so I left on over night and today and when I got back home, it was indeed stuck on 88% (nearly 24 hrs later!!).
0 kommentar(er)
