Re: Windows 10 Tool Usb Stick
Raingarda Krzynowek
I've used the tool many times in the past without any problems but since September I can't get it to work. I've tried media creation tool versions 1903 and 1909. I'm even holding on to old Windows 10 v. 1809 USB sticks because of this.
EDIT: Apparently the problem is with my computer. The same version of the media creation tool and the same usb drive worked fine in another computer. Does anyone know where the log files for the creation tool are stored?
Having an about 10 year old i7 machine, I want to re-install Windows 10 Pro over the existing Win10 Education installation using a USB stick. But when booting the Win10 iso, I only get a black screen with blinking cursor. Nothing happens, even not after waiting for a longer time. The used ISO file was generated using Microsofts Media Creation Tool.
Another trick... wait it out. I was using the October build on an ancient T3400 dell quad core. It was flashing. I was messing with my phone for 5 minutes and it proceeded to the install. Let it sit awhile. Might work. Worked for me.
Not much. The best thing would be not using Windows, since Windows 10 contains forced updates. So even when you use tricks to install an older release, Microsoft will update it very soon without asking you. When you're in the situation like me that you're forced to use the Windows installation (yet), it seems that you must live without VT-d.
HeiDoc was quite usefull here, since downloading special versions is a big mess on Microsofts side: The current official Media Creation tool didn't let me choose any parameters about the version. Even when using an older version of the tool itself, it doesn't start and force me to download the latest version.
I tried installing 1709 on USB stick which works perfectly. Since Win10 has forced updates, I'm surprised if the system is working after installing the latest auto-updates, which bring the system up to 1803.
I had a similar problem a few hours ago (black screen w/cursor after trying to boot from USB on an old computer, despite that same USB working on newer ones), and user Igb suggested that I try using a program that "helps you boot from a number of sources", called Plop Boot Manager:
You'd have to burn the downloaded ISO onto a CD/DVD (or another flash drive) and boot from the disc, then select the USB drive and try to boot from it. It worked perfectly well for me, so might be worth to go for it and see what happens.
Used Rufus and tried manual ISO build to USB with powershell. When trying to boot from the USB, the windows blue background displayed foe a splot aecond then went to the flashing cursor and seemed to hang. I left the machine on over night in that state and next morning it was showing the setup screen - just needed patience. It was odd the windows loadong background showed up and then displayed the cursoe for ages - assumed it had hung.
I am having a similar problem. I'm trying to install Windows 10 on an old HP All-in-one (TPC-Q003) which belongs to a friend of mine.I've created a bootable drive with Rufus and apparently the motherboard is compatible with UEFI, but when I try to start the installation, it shows the Microsoft logo, then the screen turns blue and I get the blinking dash.I saw a lot of people online talking about waiting it out, but it blinks for maybe a minute or two and then the computer shuts itself down. Any ideas on how to work this around? Thanks in advance.
When it is done, take the drive and put it back in the computer you were trying to install W10 on. Boot the system, and after a bit of setup you should be taken to the screens where you have to create a User Account, etc.
It is basically poor UI design, I think Microsoft want you to do the upgrade from a running OS. Nevertheless, this is not really forgiveable, there should be some indication that boot has occurred or is progressing.
So, just laziness on the part of the publisher. Perhaps there is a technical barrier to having a splash screen? I would think that if they were halfway competent they would find a way. Even Windows 95 was better than this.
Microsoft Surface Data Eraser (legacy) is a tool that boots from a USB stick and allows you to perform a secure wipe of all data from a compatible Surface device. A Surface Data Eraser USB stick requires only the ability to boot from USB. To learn more about the data wiping capabilities and practices Microsoft uses during the service process for Surface, see Protecting your data if you send your Surface in for service.
This version of Surface Data Eraser is not compatible with the latest Surface devices including Surface Pro 10 and Surface Laptop 6. For these and all subsequent devices, see Surface Data Eraser (IT Toolkit).
After the creation tool is installed, follow these steps to create a Surface Data Eraser USB stick. Before you begin these steps, ensure that you have a USB 3.0 stick that is 4 GB or larger connected to the computer.
When the Congratulations screen is displayed, you can eject and remove the thumb drive. This thumb drive is now ready to be inserted into a Surface device, booted from, and wipe any data on the device. Select Complete to finish the USB creation process, as shown in Figure 5.
If your device does not boot to USB using these steps, you may need to turn on the Enable Alternate Boot Sequence option in Surface UEFI. You can read more about Surface UEFI boot configuration in Manage Surface UEFI Settings.
The Surface Data Eraser script detects the storage devices that are present in your Surface device and displays the details of the native storage device. To continue, press Y (this action runs Surface Data Eraser and removes all data from the storage device) or press N (this action shuts down the device without removing data).
The Surface Data Eraser tool deletes all data, including Windows operating system files required to boot the device, in a secure and unrecoverable way. To boot a Surface device that has been wiped with Surface Data Eraser, you first need to reinstall the Windows operating system. To remove data from a Surface device without removing the Windows operating system, you can use the Reset your PC function. However, this does not prevent your data from being recovered with forensic or data recovery capabilities. See Recovery options in Windows 10 for more information.
Surface Data Eraser v3.2.45.0 and above can be used to restore Surface Pro or Surface Laptop devices with the 1TB storage option in the scenario that the device shows two separate 512GB volumes or encounters errors when attempting to deploy or install Windows 10. See Surface Pro Model 1796 and Surface Laptop 1TB display two drives for more information.
The Surface Data Eraser USB drive creation tool is unable to run on Windows 10 S. To wipe a Surface Laptop running Windows 10 S, you must first create the Surface Data Eraser USB drive on another computer with Windows 10/11 Pro or Windows 10/11 Enterprise.
[Moderators of this forum, I am not sure whether I am allowed to mention a third-party tool. Therefore, Apologies if I negated any rule(s) and you may remove my comment but only after @fedorauser2 has read the same.]
You need to format your USB stick with a filesystem first if you plan to use it in a Linux or *BSD distro. However, if you plan to write an ISO file to said USB stick using Rufus in a Microsoft Windows environment, you do not need to format it with a filesystem. Rufus will take care of creating the appropriate filesystem for you.
It does, but I have not had 100% good luck trying that.
If running linux then gdisk or gparted can easily be used to create a new partition table and gparted can format the file system. If using windows then the method shown by Ariana seems the easiest and safest.
If I were formatting the USB for ntfs or vfat I would certainly use windows to do that. If formatting it for any of the linux style file systems then I would use linux since windows cannot format those file systems.
The issue I had with Etcher on an USB stick a year ago or so was solved. It was most likely no problem with Etcher for me, nor the USB; it was my lack of knowledge about those different file systems which are created when burning the ISO file for eg Linux installation, and that Windows and macOS cannot really recognize Linux file systems.
I observe that it is the Create Partition Primary command in DiskPart.exe, rather than the Recover or Clean, that restores the Volume back to RAW and Healthy. Then a Windows Disk Format succeeds in setting the format to FAT32.
I understand that tool changes the disk format to suit Linux and this is incompatible with Windows. However it is clear to me that in the process the tool trashes the drive (as far as the Windows environment is concerned) before it completes the transfer of the ISO image.
Obviously the tool has to be able to write the image successfully in the Windows environment before changing the disk format to suit Linux. It also needs to be able to restore the disk format back to suit Windows for further updates. So that the user does not need to resort to using something like DiskPart.exe to do this.
Happy it worked for you.
Rufus is a software that specialises in creating bootable USB sticks for windows. In contrast Etcher really only flashes an image but makes no attempt to make it bootable. So if your image has issues booting on your target system rufus might be the better tool.
Hi,
flashing from a USB stick seems allright to me.
On windows the device will only show up if it contains a recognized file system and on linux it only shows up in df if it was mounted.
In linux you could use gparted or fdisk to examine the drive. lsblk will show you the block devices in your system, you can run it with and without the SD-card to check which device it is. On my computer an SD card will show up as /dev/mmcblk0.
Description: SystemRescue (formerly known as SystemRescueCd) is a Linuxsystem rescue toolkit available as a bootable medium for administrating orrepairing your system and data after a crash. It aims to provide an easy way tocarry out admin tasks on your computer, such as creating and editing the harddisk partitions. It comes with a lot of Linux system utilitiessuch as GParted, fsarchiver, filesystem tools and basic tools (editors, midnightcommander, network tools). It can be used for both Linuxand windowscomputers, and on desktops as well as servers. This rescue system requires noinstallation as it can be booted from a CD/DVD drive orUSB stick, but it can beinstalled on the hard diskif you wish. The kernel supports all important file systems (ext4, xfs, btrfs,vfat, ntfs), as well as network filesystems such as Samba and NFS.
d3342ee215