How to Transfer Files from Windows to Linux on a formerly Dual-Booting configured Machine?
 

I can no longer boot into Windows after messing around with my partitions. Before I wipe the disk to free up some space I wanted to retrieve any surviving files from Windows.

from your file manager, you should be able to click on the windows partition and copy files off of it. If not post the output of so we can see if your windows partition still exist and what partition it is on

Are you allowed to link to other threads? I just want to give you an idea of everything that was done so far so that we don't accidentally repeat a lot of the same stuff.

can you still boot your linux? if yes then file manger into it, or mount it then go in that way, or live usb stick and go in that way to get your files out of windows.

I can still boot linux, I spent the last week with rknichols helping me get to that point. Now I just need to get my files from the unbootable windows back if possible.

this line from your output you are looking for is:

That tells you it is on sda3.

https://linuxconfig.org/how-to-mount...d-write-access

read up, that should help, best of luck.

Much obliged, thank you.

if the information helped, please mark this thread solved.

Thank you.

Unfortunately not,

looks like you need a windows repair disk. install disk, winpe iso something similar so you can run chkdsk, files still may not be recoverable based on your previous threads

can you install winpe on linux? to be clear, are you suggesting to reinstall windows and then run checkdisk to find the files? would it be possible to do so on a virtual machine?

no run chkdsk from a windows installation/recovery cd/iso/usb

https://www.microsoft.com/en-us/soft...d/windows10ISO
https://www.ghacks.net/2018/05/25/wi...le-usb-woeusb/
https://neosmart.net/blog/windows-recovery-discs/

repair mbr, boot might do you some good, looks like it may have been using hibernation that is why it is telling you its screwed up via linux. but you need a version of your windows install disk to repair it.

https://www.easeus.com/partition-mas...indows-10.html

if it fixes you'll be booting windows like no linux installed, then before you do this created a supergrub2 boot usb stick , it might get you back in, its been a long time sense I've had to use that in this particular issue. maybe a usb live to reinstall grub.

The easeus people want money for all the software that you need to follow these instructions. The free versions do not allow you to use the part of the software needed. Likewise the software I found to mount the windows .iso image says the image is too large to mount on the current usb that I have, so I'll go to the store today and get a larger USB and an external Hard drive.

If you still get a file to large error install woeusb, It may be in fedoras you may be able to install with https://fedora.pkgs.org/29/fedora-up...86_64.rpm.html
from your fedora
use woesusb from the command line when you run WoeUSB from graphical menu it automatically reformats the usb to fat32. Start WoeUSB from the command line with something similar to this

the sdx will be different and the iso may be named different.

Refer: https://github.com/slacka/WoeUSB/wik...ize-limitation for more info

I'm getting this error:

Also, going through the graphical interface still fails because "in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed.

mmm how about destination path???

It would be this if the iso is in your Downloads folder and your in your home directory. Change sdb if your usb isn't sdb.

[root@localhost ~]# woeusb \
> --target-filesystem NTFS \
> --device Downloads/Win10_1809Oct_English_x64.iso /dev/sdb

woops

The file is "Win10_1809Oct_English_x64.iso" in /home/madmin/Downloads

It is sdb, but for some reason in Disks the size slot is blank, should say something like 32 GiB. The iso is in the downloads folder

so it will be:
woeusb \
> --target-filesystem NTFS \
> --device /home/madmin/Downloads/Win10_1809Oct_English_x64.iso /dev/sdb

[edit] Hang on there was a typo

Here's the file list for my root directory just in case:

OTay
first to find where to go to..
gives you mount points, pick the right one.
cd into where your iso is at then issue the command from there, else give it absolute path to iso.
try getting a new iso...

Still no luck, with everything typed in properly I'm getting this:
When I tried to format the flash drive, I chose to erase everything on it (warning this will take longer etc.), it took a half hour because it's 32 GiB. Before I did this the size of the flash drive said something like 27 GiB in the disks graphical utility, but afterwards it just shows a blank. Did I ruin the brand new flash drive already...

No sdb
 

I unplugged the flash drive and put it back in and now it's showing it:

From sandisk:

Unmounted:

cheers

Oh SH^^ if it does not have root use sudo

sudo umount /dev/sdb1

sudo woeusb \
> --target-filesystem NTFS \
> --device /home/madmin/Downloads/Win10_1809Oct_English_x64.iso /dev/sdb

Fedora uses sudo by default.
sudo su will let you become root

Now the file manager is showing an "UEFI_NTFS" and a blank "Windows USB" where the flash drive was

If you didn't get no errors, see if it will boot.

I tried to boot from the UEFI flash drive and got this in big yellow letters:

'\efi\boot\boot x64.efi': [14] Not Found

also sdb split in two:

did it show you a directory tree of sorts that you can navigate through it and look for a file to try booting it? (mine does)

It hadn't, but I just went through the process again and is says target device should be bootable now.
I wonder if it is because there were actually files to be overridden this time that it worked. Another question I have is why the graphical utility had a maximum file size but the terminal command did not. I'll try booting now and let you know the results.

I didn't get that error thankfully and it booted, I'm sending this from my phone now. I'm sitting at the choose an option menu. My next step according to your earlier suggestions is to run chkdsk. My choices are to do a recovery or install.

recovery first, to see if you can fix your mbr and boot list, you're going to lose linux grub but that is be gotten back..

Unfortunately it needs a serial key to install which makes this basically useless. I'll try to fund a recovery specific windows 10 iso.

did you try recovery yet?

also I just hit skip on that key thing and install and they have the key on the server with win 10, second time I had to install win10 it skipped the key thing and it is still a valid install os. but if you install you might lose your stuff, so again try repair to fix your mbr and boot list.

Ntfs doesn' have the file size limit that Fat32 has and the file size limit is exceded by the iso. The graphic utility defaults to fat32 which can be overridden when done from cli

Repair failed, and I hear you on the installation precaution. I'm at a command prompt and I ran chkdsk but it only processed 7 files. Are these just on the usb?

What happens if at the cmd:
cmd: C:
cmd: chkdsk

I have no idea I am not there looking at it, to ever try to figure that one out.

"Errors found cannot continue in read-only mode."

boot usb get to cmd
Don't do cmd C:

I did that and nothing seems to have happened

did it come up with any errors, or the read only error again. Maybe you didn't give it long enough. As said in an earlier post, still may not be able to recover files if chkdsk can't fix the filesystem. maybe there needs to be a space between C: /r

[edit] chkdsk c:/f is running now (I was writing cmd before it) right now C:/r is running there's about an hour left

Chkdsk completed it says it made some recoveries, reallocated space and moved around some files. Still no luck booting into windows