Windows 10 Installation on a SSD error: " We couldn't create a new partition..." - windows

I have an Acer Nitro 5 with a Gigabyte 512gb ssd and a WD 1TB hhd.
Recently after installing Ubuntu on my hdd (because i didn't want to change the sata mode), I also wanted a clean Windows install. So I created a boot usb from
media creation tool and go forward with it.
It didn't work. I got the "We couldn't create a new partition or locate an existing one" error, which i spent a significant amount of time trying to search for a solution.
Stuffs i tried:
- Format my ssd
- use diskpart to clean, convert my ssd partition table to gpt, etc like every guide online recommends.
- Make another boot usb, this time with rufus. Didn't work.
Stuffs I didn't try:
- Temporarily disconnect my hdd. I don't have the tools to do that physically, and my acer uefi has zero options regarding this, like most guides suggests.
- Change to bios-legacy boot mode. There's no option in the uefi.
I think it would be fine if i try to install windows on my hdd though, but haven't try it yet. All I know is installing windows on a ssd is much harder but didn't expect it to produce this much annoyance.
I heard there's an option to install on a HDD, the. use a third party tool to copy it to a SSD, but i haven't look into it.
Thanks for any help given..

Assuming you have Windows 10 installed and working on your SSD go to Settings > Update & Security > Recovery > Reset this PC > Get started and then select if you want your files kept you want clean reinstall. Again - from your post I assume the latter so just click Remove everything" confirm and wait. It will take (depending on the machine) 1-2 hours.
I've found this to be the easiest way to have clean install without wondering how do I get it installed on my laptop/pc.
My recommendation though - back up your ubuntu partition - I can't guarantee that windows installer won't clean up HDD you have (it's supposed to clean only SSD but better be safe than sorry).
Here's the link to detailed instructions. It's based on 1903 compilation - if your's older it will still look very similar.
If your windows isn't working then use diskpart to clean the drive, boot the computer from USB windows installation stick and choose the drive for your installation - it will/should create appropriate partitions and start installing.
If it won't change boot order so the SSD is first on the list and HDD next and repeat the previous step.

Related

I Installed windows on a new ssd and I lost Ubuntu on another hhd

Now, the only working operating system is Windows 10. When I go to my Pc in windows, I don't even see my hhd. Is there anyway to save this mess? I tried to unplug my ssd and see if ubuntu shows but nothing.
You probaly go two problems here, the first one is:
the only working operating system is Windows 10.
You probably just replace the default boot drive with the drive where Windows is installed, in this case, you will need to change the boot order, and place the HHD where ubuntu is installed as the first option on the boot order list, (this guide can give you some idea of how to do it. ) after this you will probably see the grub system selector page when your PC starts.
Now to the second problem:
When I go to my Pc in windows, I don't even see my hhd.
The reason that Ubuntu drive doesn't show up is that Windows and Ubuntu use different types of file system technology. Windows uses NFTS and Linux (Ubuntu, Debian, etc) uses EXT4, Windows doesn't support EXT4. To see the Ubuntu drive on Windows, you will need to divide the Ubuntu drive into two partitions, one EXT4 for Ubuntu and another one in NFTS.

StoreMI - Create Bootable StoreMI greyed out

Situation: New PC Build
- Windows 10
- Samsung Evo 970 256GB NVME
- WD Blue 1TB potato drive
- AMD Ryzen 7 2700X on Asus Crosshair VII Hero
- GTX 1070
One of the main benefits of Ryzen 2, for me, was the StoreMI feature that I really hope to get working. I watched AdoredTV's video of how he set his up, but unfortunately for me, I'm not having any luck.
Greyed Out no option to create Bootable StoreMI
I have gone into Windows Disk Management and made sure the drives are visible to the OS, and they are also visible in File Explorer.
Windows Sees the Drives
If I try to remove fast media, I get this message, and the program closes.
If I try to modify, I get nothing useful.
So...I need some help figuring out what I've done wrong. Could I have something in the BIOS I need to fix? Other? I'm at a total loss.
Edit 1) I may have another clue? One of my greyed out drives is the same drive as the drive that's selectable, and they're "both" in a Tier. Looking at the Disk Manager, it seems my "System Reserved" is for some reason on the NVMe drive when it should have...I would have thought...been installed on the same drive the OS was installed on. I know I didn't tell Windows to do this.
So maybe this is a clue? Can I move the "System Reserved" Partition over to the spinning rust? Would that help?
Same Drive occupies both tiers?
Ok, well AMD customer support never emailed me back. It's been about 48 hours now. Not counting the RTFM email which was useless.
So...I figured...Maybe I'll ask the people I learned the most about this from, either AdoredTV, or Level1Techs. So I went to the Level1Techs forum, and talked to Wendell himself. He diagnosed and suggested a fix (that worked) in about 5 minutes. On my Windows install, I selected the C: (slow) drive to install the OS on, however, the OS set up the "System Reserved" partition on the NVMe drive...even though I never said to do that...it never asked if that's what I wanted to do...It just did it. Effectively nullifying the ability of StoreMI to work.
Why AMD can't do what a youtuber can in 5 minutes is beyond me...and pretty inexcusable. But I digress...
What I had to do was start over. Backed everything up, inserted my Windows 10 installation USB, booted from that, and ****-F10 into a command line from there.
From there, I cleaned all my drives.
Next, I physically removed my NVMe from the motherboard, then went about reinstalling the OS on the slow drive...now the only drive in the system, so it was forced to partition that.
Once that was done, and the OS was completely installed, I shut down the system and reinstalled the NVMe.
Rebooted the system, and I was then able to configure StoreMI easily.
TLDR: If you are doing a new system build, with a fresh Windows install, and want to use StoreMI... My recommendation is to install ONLY one HDD into your system (AMD recommends the install take place on the slowest drive). Complete your Windows install, then install the remaining drive or drives (you can only use two drives with StoreMI), install StoreMI and configure.

Unable to install windows from usb flash, I get an error "setup was unable to create new system partition"

I have CD with window 7, I can install windows from this cd, but disc is't mine. So, I want to make a copy on my usb flash drive. I made iso copy of cd disc with WinISO, then I wrote this iso file on my flash drive with "Iso to Usb".
Now I try to install windows from this flash. I have 1tb hdd, I created 100gb partition and get 100gb partition, but when I did the same with with Windows cd disc, it creates 100 gb primary partition and 100 mb system partition.
So, when I tried to install windows in 100 gb partition from cd it installed, but when I tried to install from usb I got exception: "setup was unable to create new system partition".
Why so? Why I do the same steps and I can install from cd, but can't install from usb?
Why usb windows didn't create system partition? And how to fix it?
When installing using a flash-drive perform the following steps:
Step by step instruction:
When the boot setup starts from USB drive
Press Shift+F10
The command prompt will open.
In console type diskpart.exe and press enter. In this program execute following:
select disk=0. Disk 0 is your destination drive, so be careful, all information on this drive will be removed.
create partition primary size=xxx, where xxx – is the size of new partition
select partition=1
active
format fs=ntfs quick
assign
exit
4.exit
5.Now close the setup and restart.
This should solve your problem as it did mine.
Windows usually creates a partition with enought space for the system.
You can try to just take the 1tb HDD as target for installation, and windows will create a partition automatically.
Otherwise, your ISO-Copy may be corrupted.
You could easily download the ISO-Files from here.
Option: Make a Copy of the CD and try with that one?
Having installed windows 7 from a USB drive many times, I've found that if you're trying to install using a USB 3.0 flash drive, then you will get the "setup was unable to create new system partition" error message.
Since I couldn't find any solutions to this at the time, I was fiddling with everything to try to make it work. Eventually I found out an interesting (but strange) solution:
Go through the install process until you get to the screen that asks you to select a partition for the windows installation
Make sure your desired partition is listed, and that its formatted correctly
Unplug the USB drive
Press 'Refresh' (ONCE) to refresh the partition list/window (ONLY press refresh)
Plug the USB drive back in (use the same port as before)
Select the destination partition for the Windows installation, and try to begin the installation
I've done this a few times now on different machines, and it's worked like a charm.
I believe it has something to do with Windows 7 not natively supporting USB 3.0 and/or USB drives with SSD controllers.
Windows is probably seeing the USB drive as the main hard drive, because you have probably made it the first boot device in the BIOS. This will result in Windows trying to install to the install drive.
To solve this problem, make the internal HDD the first boot device, then press F12 or whatever key for boot device selection your BIOS requires.

Recover windows seven

I started on Ubuntu and have had the first considerable error. I'm looking for help.
I have an HP Pavilion dv6 i7. I had installed windows 7 and I decided to also install Ubuntu using a USB.
My first attempt was to install Ubuntu 11.10 following the instructions of the official Ubuntu website. When loading the pendrive, my PC stucks at the main menu of ubuntu, so after searching, I found could be due to a problem with my AMD Radeon graphic card (or not), but I decided to change.
Then I used Ubuntu 10.4. This could happen from the start menu i get into Ubuntu live. There I decided to install it because I liked it and I need to develope with Google TV (in windows is not posible).
And I fail in the partitions section. I tried to follow the instructions on this page:
http://hadesbego.blogspot.com/2010/08/instalando-linux-en-hp-pavilion-dv6.html
but there were things that changed a bit so I improvised. I took the windows partition of 700000MB and went to 600000Mb leaving 100GB free to install Linux there. The error was to set it to ext3 (it was ntfs). I thought the new 100gb partition will be set to ext3, and windows partition will stuck at ntfs system, but not.
Total I ran out to boot windows, and above I can not install ubuntu on the 100GB free.
Someone thinks I can help. Is there any easy way to convert back to ntfs windows and not lose data?
Thank you very much.
You should be able to hit F11 when the machine is booting up and go to the HP recovery application. This should let you reset to factory default.
You should definitely be able to install Ubuntu on the new 100GB partition as well. Just make sure you choose the right partition to install it on.
You will need to recover using recovery CD/DVD's. You must have been using the install gparted utility in Linux to "re-partition" your drive. You scrubbed some boot files.
If you successfully recover using the recovery media you can use Disk Management in Win 7 to shrink or extend your volume. In your case you would shrink it down 100Gb's and then when installing Linux gparted will see that available 100 GB and install there while Windows will still run.
Also, you should probably be running ext4 fs, not ext3. you would only want ext3 for compatibility reasons.

Quick creation of fresh OS install for software testing

What do you recommend for quickly creating images for testing a software product (that needs hardware access - full USB port access)? Does virtualization cover this? I need to be able to quickly re-image the system to test from scratch again, and need good options for Windows and Mac OS.
Virtualization may work for you as long as it is only USB access.
VirtualBox is available with USB support either for "private use or evaluation" or commercially and works on Win, Mac and Linux. USB support on Linux and Mac is somewhat sporadical though and does not work with all devices. VBox supports snapshots.
VMWare has one free product called VMWare Server for Win and Linux but I'm not sure how far USB support is included in their server products. For Mac there is VMWare Fusion but that's not available for free. Fusion should work with most USB devices. Workstation products for Windows are more expensive. I think there is a trial version for all of them. All do snapshots.
I don't know how far Parallels (Mac) supports USB devices or snapshots.
You don't need snapshot functionality if you can afford some short downtime between re-imaging. You can shut down the VM and then just copy the disk image (which is nothing else but one or multiple regular files) and start the VM again. Snapshots can be reverted to a lot faster (without rebooting).
If virtual machines will work for you, you can choose between Virtual PC, VMWare and VirtualBox.
Virtual PC supports Win host and Win/linux guests. Although there are some caveats with regards to the X resolution support.
VMWare supports Win, OS X and Linux host. It supports Win and Linux guests.
VirtualBox supports same hosts and guests as VMWare.
None of the three supports OS X as guest officially. The reason is that OS X is licensed only for Apple machines. However, there are some hacks that allow installing OS X under VMWare. It might be also possible to install it under VirtualBox or Virtual PC, although I have not seen specific instructions.
If virtualization is not good enough for you, you can use precreated installation images or a disk imaging program.
For precreated installation images for Windows, you can use the sysprep tool (search for sysprep or system preparation tool). I don't know if there are equivalent tools for OS X from Apple.
For disk imaging programs, I know quite a lot people swear by Symantec Ghost. I personally have not used it, so can't give you much info about it. There's also a list of disk imaging programs on Wikipedia, so you evaluate these as well.
Hope that helps.
If virtualization is right for you depends on how much access direct access you actually need.
But if virtualization works then vmware offers products for Windows and Mac that support a Snapshot feature.
Or there's also VirtualBox which works on Linux, Windows and Mac, also supports snapshots and is free.
I use VMWare Player for this sort of stuff. I've not tested it with the sort of access you discuss (since I mostly do apps rather than driver-level stuff) but the advantages are many, specifically being able to copy the VM when it's shut down for later restore to a specific point (sort of a poor man's snapshot) and being able to have lots of configurations without blowing the hardware budget.
It certainly provides USB virtualization and I would say it's the best bet for providing the full device access. I would suggest testing it since, if it provides the hardware support you need, it's a very good solution for the other reasons given. The only other (non-VM) suggestion I can think of which would match it would be hard disk image backups which can be restored at will.
I've used Virtual PC heavily for this kind of thing in Windows, without ever hitting any issues. It's free, which is always a bonus ;o)
Edit: Just re-read the question - not sure that it has USB support. Should tick all the other boxes though
CloneZilla is a great, free way to reimage machines.
Once I worked for some company where we needed to test our software for various combinations of versions of OS, SPs and some other libraries which our application was dependent on. For each separate identified combination we had a separate partition image created with the help of Norton Ghost (DOS version). All images were put to a server. Whenever a tester got the next version of the system core to test, they would just methodically restore from all applicable images, install the application, test it and report it.
This approach though a straightforward one would allow full access to the hardware and will provide you with 100% native installation.
Nowadays, I still use this approach for my private PC. I'm sure you can try the latest achievements like Hyper-V. We use it nowadays where I work. When we tried to install Team Foundation Server (the process is far from being easy) we also had to drop the process at some point and just restore a virtual machine from an image because we realized we made a few mistakes during installation. Conceptually the same approach that saves a great deal of time. I'm not really sure though how compatible a virtual PC is in the sense of hardware access.
You can try both approaches.
P.S. Today there are two Ghost products, Symantec Ghost (good old one) for corporate use and Norton Ghost for home use (bloatware in my opinion). If you decide to try this option, I would recommend the Symantec Ghost (part of Ghost Solution Suite).
If you can't just use a virtual machine and take snapshots of the fresh install then do a fresh install onto real hardware and use a disk imaging tool (Ghost comes to mind).
If cost is a factor then there's a few Linux live CDs that will do what you want. This comes to mind. Put a second disk in the machine and image from the second disk unless you have fast networks and network storage; it's way to slow to go to and from the network regularly. If you're using a Linux live CD then you can actually set the second disk to EXT3 so Windows won't detect it and assign a drive letter too.
If you have a dedicated workstation for testing then I would highly recommend Symantec Ghost. Simply get the workstation to the clean state, reboot to ghost and 'take a snapshot' of the HD or partition. You can then replace the HD or partition from the image say from CD or multicasted over a network connection from another PC.
I have used it for years now, even to the point of automating the build of 60 test workstations (at the same time).

Resources