It may be just file corruption. Try running chdsk.exe /f C:
in the command prompt. If that doesn't work, try dism.exe /online /cleanup-image /restorehealth
. Keep your virtual NIC online for the second command, it may try to download updates from MS if local files are corrupt and the WinSxS backups are corrupt as well.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Thanks for the answer! The first command says chdks.exe is not recognized as an internal oe external command
, and the second commands says Error: 87 cleanup-image option is unknown
Sorry, chkdsk.exe /f C:
... it was late, I was tired 🤷.
Error: 87 cleanup-image option is unknown
Try it without the cleanup-image
switch.
It says "cannot open volume for direct access" :(
Running the second command without cleanup-image flag says the same thing for restorehealth, and running without it too well, has no options after /online so fails
Thank you very much for your time!
The prompt doesn't run as admin. Try this command, should open up a second command prompt as admin: runas /username:{AdminUsername} cmd
.
You can boot the VM from a liveCD ISO and then mount the drives to extract files (share a USB storage device to easily get them off). You could also add a second virtual disk, put an NTFS partition on it (within the VM) and copy to that if you plan to rebuild the OS drive.
If you need the offsets of the partitions you could also mount them from the disk image directly via a loopback device, but that's a bit more complicated.
When dealing with Windows either on bare metal or VMs, I've often found it useful to store my more important data on a second disk so that I can easily back it up and it will survive across a wipe+reinstall of the OS.
I achieved to retrieve my files!!! thank you very very very much! Now I can try more "dangerous" way to resurrect it because my data are now safe in my USB drive
Glad it worked for you. Your could also try and of the recovery options after booting from a Windows ISO. I think there are a few things that can do there that aren't in the boot-failure recovery menus.
If not, then at least your data is safe for a reinstall
Can you post a screenshot of the BSOD? This is really not much info to go on :)
But if you can access the command prompt, then your installation is still accessible, and so are your files. But its easier to diagnose if we know the actual error codes etc.
Thanks for the answer! There is no error code, the first thing showing up is a blue screen that makes me choose the keyboard layout, and after it the various recovery options (cmd, uninstall updates, etc)
So no BSOD then, you enter the preboot.environment :) does it also say "continue to boot to windows" or something?
I dont think you need to reinstall, theres several ways to fix it :) we just have to figure out how knowledge you have, and what options the preboot environment has ;-)
I... I... I don't know what happened, I was doing random stuff in the bios and... It booted up... Finished its upgrades.. And now it's working.... I have no idea what happened...
Well that settled it then. You're an IT expert. 😂
But really, try booting a portable version of Windows like it's a CD or USB in the VM.