Windows 10: Automated USB repair disk to restore Windows 10 back up from UNC path.

Hi All, I am new to forum but looking for some advice. I have made a full Windows 10 backup to a network UNC path. I have created a windows 10 restore USB disk and tested the restore by booting up with the Restore USB disk this works fine. BUT, I am looking to automate the USB Boot disk so it automatically restores from that image with out any user input. Does anybody know if this process can be automated by adding an answer file to the windows 10 restore USB disk?

:)

 

Windows 10 USB boot

Hi there, am not a windows 10 expert. I have a pc in the bedroom on windows 10, I messed up the bootloader trying to fix the xp on that system.

System wont boot, trying to repair via win 10 usb installer.

Downloaded the media creation tool to install windows 10 installer on usb stick. Not compatible with a host of usb sticks I have. Tried the usb sticks that others use, but I think they use rufus; as the media creation tool by win 10 does not detect the usb stick.

So quick question, the win10 machine i am trying to repair the bootloader is a win7 upgraded to win10.
If i were to use the usb win10 installer to "repair installation" does the version of the iso downloaded via the media creation tool matter?

There is three options:
Windows 10
Windows 10 Home
Windows 10 N

Also is there a step by step instead of using rufus as I want to try an alternative method of creating a usb win 10 installer. Preferably with more compatibility.

System is a asus sabertooth 990 (r2?) with AMD phenom X 6.

Also is there any other software I can load onto the usb that can repair the bootloader easily?
That would be the ideal alternative. Thanks

 

UNC paths

OK, So here is the problem

I am used to the structure of a Linux /dev/sd?? filesystem

When I am using Windows I want to virtualize this Linux installation..... but I can not point VirtualBox to the block device (or whatever you wish to call it for) used in windows 10

I have tried

VBoxManage.exe internalcommands createrawvmdk -filename "d4p7.vmdk" -rawdisk "\\.\Device\Harddisk4\Partition7"

I have also tried

VBoxManage.exe internalcommands createrawvmdk -filename "disk4part7.vmdk" -rawdisk "\\.\PhysicalDrive4" -partitions 7

This just makes a link to the entire disk, which I do not want, I the UNC path for the partition on disk 4 partition 7

I don't even know how to browse the UNC directory to find the answer myself

CAN someone please help me

 

One specific UNC path suddenly not working on one specific Win10 machine

Hi,

A month or two ago, my main computer stopped being able to access my NAS' UNC path (\\corbeau\...). It used to work.

• I do not remember changing anything on that NAS
• Other Win10 machines can access that same UNC path
• The problematic machine can access the NAS by using its IP in the UNC path (\\192.168.2.10\...)
• All machines can access other machines by their UNC path (\\cardinal\... or \\epervier\...)
• A ping for the NAS name from the problematic machine fails to resolve
• Pings from other machines work
• Every machine can ping other machines by their name

I'm totally lost. Where should I look for to resolve this very annoying issue?

Thanks.