locked
Install Failure: unable to create a new system partition RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi guys (and gals),

    I'm trying to install Windows 7, however at the partition selection screen I get a "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information." I'm not sure where these log files are but I have no idea why this is happening. Í'm trying to install the 64-bit version of Windows 7.

    Anyway some system info:
    AMD Athlon 64-bit dual core 2.4Ghz
    5GB ram
    I have 3 disks
    one 500GB 
    another 200GB
    and one 100GB

    I have an nVidia chipset and a sata setup (no raid config)

    on the last one I have one extra partition with 60 gigs of room and it's now completely empty and it used to be my vista drive. I tried formatting it, removing the partition, recreating it then formatting it again. Formatting through the cmd prompt in the recovery section and formatting through geparted, and all the partitioning stunts I could think of. I've not had this issue with the Vista (64-bit) installation, I've seen some reports of people having this issue. I also noticed a post here regarding nvidia chipset raid-0 and the windows 7 installation, however for me it hasn't been working out as it informs me that there was no valid kernel found on the new disc. So my questions are: why is this happening, and how can I solve it?

    If you need more information I will gladly give it to you, but I'm right now, not sure what more I should write here.
    Wednesday, January 14, 2009 9:36 PM

Answers

  • Question
    Sign in to vote
    11
    Sign in to vote

    I have since successfully installed Windows 7 (in various flavors) on multiple machines, including my own! 

    The process for dealing with this error is SIMPLE:

    Unplug every EXTRA hard drive in your system, EXCEPT the one you intend to install the OS on.  (This includes extra USB flash drives that have installation drivers on them, ie., F6 setup disks) 

    If install drivers (F6 setup disk) are needed, do NOT insert usb flash drive until prompoted to do so by the Win 7 setup program.  (Windows 7 setup see this drive as another viable partition most of the time if inserted too early, and it stalls the install giving the error people reported in this thread.

    After your installation has succeeded, then go in and plug-in all other SATA, PATA, USB, and firewire HDDs.  Windows 7 will now plug & play them all without further problems!

    GREAT LUCK TO ALL.  ENJOY USING WINDOWS 7 everyone!!!

    • Proposed as answer by usnbrendon Thursday, May 6, 2010 9:03 PM
    • Marked as answer by Carey FrischMVP Thursday, December 29, 2011 3:05 AM
    Thursday, May 6, 2010 9:03 PM
  • Question
    Sign in to vote
    4
    Sign in to vote
     All right here's the answer:

    For me the problem was that I had one disk that had a partition on it labeled "Dynamic disk," apparently Windows 7 setup does not know how to handle this and just gives you a generic error saying that it's unable to create a system partition.

    The steps I took where:
    First only plugin the disk that I wanted to install to. This had no partitions on it what so ever and was completely empty. Windows 7 setup would install to the disk creating the two partitions on its own (so that's with the 200 MB recovery type partition).
    To check that it actually was that one disk with the dynamic disks option on, I also added the other disk that wasn't dynamic and started Windows 7 setup again. This time it would still install. Adding the other disk instead of this one (keeping only 2 discs where one is dynamic), it wouldn't let me install.

    In the end I created partitions on mij 200 GB disk, one 80 gigs and the rest on the other partition. I installed windows 7 on the 80 gig partition and I'm happy to report that it's running smoothly now.
    • Marked as answer by AlexRies Friday, January 16, 2009 10:54 AM
    Friday, January 16, 2009 10:54 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi,

    Can you take a look at this KB article:

       http://support.microsoft.com/default.aspx/kb/927521

    It describes where to find the setup log files.  In particular if you can find setupact.log and post the last bit of it (especially any ERROR lines), it might be helpful.

    Without further information here are some guesses as to what might be going wrong:

    1) You need to load drivers for your disks so you can see them on the partition selection screen.  You can press F6 or or click the Load Driver button under Advanced options and then point setup to the .inf file for your driver.

    2) You may need to adjst some of your BIOS settings so that your BIOS is aware of this disk.  That might be changing the boot options so that the disk in question is listed as a disk that you can boot from.

    I hope that helps, please post the logs if you can find them.  Thanks for trying the beta,

    Richard
    Thursday, January 15, 2009 12:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Richard Russo [MSFT] said:

    Hi,

    Can you take a look at this KB article:

       http://support.microsoft.com/default.aspx/kb/927521

    It describes where to find the setup log files.  In particular if you can find setupact.log and post the last bit of it (especially any ERROR lines), it might be helpful.

    Without further information here are some guesses as to what might be going wrong:

    1) You need to load drivers for your disks so you can see them on the partition selection screen.  You can press F6 or or click the Load Driver button under Advanced options and then point setup to the .inf file for your driver.

    2) You may need to adjst some of your BIOS settings so that your BIOS is aware of this disk.  That might be changing the boot options so that the disk in question is listed as a disk that you can boot from.

    I hope that helps, please post the logs if you can find them.  Thanks for trying the beta,

    Richard



    Hi Richard thank you very much for your reply. The point is actually that the disks are fully visible to the installer, and even 'worse' through the command prompt I can access them as you'd expect (I xcopied some stuff over for backup purposes through the cmd tool).

    The next step I've taken is to remove all partitions from my target disk creating a single disk with basically nothing on it (thus plenty of xcopying :) ). This also gave the same results. When I get home from work again I'll try to take a look at the log-file.

    A colleague of mine just came in who had the same problem he is saying that he took out his other drives (he also has 3) and installed to that single one. He pointed out that he had some dynamic disks, which I also have. He didn't really get to the source of the issue however he was able to install windows 7 after taking out his other disks. I'll be posting my log and I'll take out my disks (not necessarily in that order). Thank you again.
    Thursday, January 15, 2009 6:24 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Alex,

    Your colleague is likely to be correct. Removing data and power cables from everything but the disk you intend to install to should force the installer to partition, format and set it as active and allow your install to succeed. You can also move the drive you want to install to to the first position on the HDD bus for a similar result.

    If you have AHCI enabled in your BIOS, you may get a BSOD on booting the new install - disable AHCI and you should be good to go.

    Good luck.
    Andy.
    Friday, January 16, 2009 3:45 AM
  • Question
    Sign in to vote
    4
    Sign in to vote
     All right here's the answer:

    For me the problem was that I had one disk that had a partition on it labeled "Dynamic disk," apparently Windows 7 setup does not know how to handle this and just gives you a generic error saying that it's unable to create a system partition.

    The steps I took where:
    First only plugin the disk that I wanted to install to. This had no partitions on it what so ever and was completely empty. Windows 7 setup would install to the disk creating the two partitions on its own (so that's with the 200 MB recovery type partition).
    To check that it actually was that one disk with the dynamic disks option on, I also added the other disk that wasn't dynamic and started Windows 7 setup again. This time it would still install. Adding the other disk instead of this one (keeping only 2 discs where one is dynamic), it wouldn't let me install.

    In the end I created partitions on mij 200 GB disk, one 80 gigs and the rest on the other partition. I installed windows 7 on the 80 gig partition and I'm happy to report that it's running smoothly now.
    • Marked as answer by AlexRies Friday, January 16, 2009 10:54 AM
    Friday, January 16, 2009 10:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I had the same problem installling in a 320GByte SATA disc with three partitions: first Widows 7 32 bit, then Win7 64 bit in other partition, and third Win XP in another.
    After installing WinXP, both Win 7 were not visible because they don´t use and update the Boot.INI, and when I tryed new installation of Win 7 were not possible because the mentioned error report ("Setup was unable to create a new system partition or locate an existing ...").

    Thanks to this comment, after electrically disconecting the "Dynamic Disc" (a 320Gbyte disk for data not affected in any of this partitions) the problem was solved !!!

    Many thanks !!!!!
    Monday, April 20, 2009 4:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    SAME HERE! 

    Incredibly frustrated by a dozen or more attempts at a clean installation of Windows 7 RC1 x64 on a brand new system I just built! Win7 RC1 (x64) simply will NOT install in a RAID 0 configuration on my setup. Each time my installation process stalls with the same message:

    "Setup was unable to create a system partition or locate an existing partition."


    I cannot go any further and I am forced to end my installation and the computer reboots.  I have the latest Intel ICH10R SATA RAID drivers on a thumbdrive (instead of crappy floppy 'F6' style) and I've tried loading the ICH10R drivers from thumbdrive AND mb maunfacturer's DVD. The partitioned drives are never recognized properly by the Win7 setup apparently.  Although the patitions ARE VISIBLE and I can expand the ADVANCED OPTIONS and delete, format, etc., I receive the same error message above and can go no further. No luck with anything I've tried.  I've spent hours and hours scouring the net for answers to this issue.  Apparently this message is VERY COMMON but no one has a reliable answer at all.

    I have checked and RECHECKED my BIOS settings and have even gone to great lengths to insure that ALL non-essential hardware is disconnected during these install attempts.  I have even moved my SATA DVD connection from the ICH10 to onboard Gigaraid SATA controller. The ONLY HDDs installed on the ICH10 are the two velociraptors which are configured by the RAID BIOS and are properly recognized by the system and Win7 installer.


    My system:
    GIGABYTE EX58-EXTREME mb
    Intel i7 920 quad-core processor
    12GB DDR3-tri-channel OCZ ram
    (2) 300 GB WD Velociraptors in RAID 0 configuration
    Samsung SATA DVD burner
    Sapphire HD4870 1GB GDDR5 PCIe GPU
    ((no FDD at all, so using 8GB thumbdrive for F6 drivers))

    All additional drives (WD 1TB eSATA drive and other Raptor drives) are NOT connected at this time to avoid causing conflicts!

    I have recently read posts that indicate there are 2 log files created during each attempt at installing Windows 7. I found them in the following location: X:\windows\panther\ however, there seems to be no usable information contained in these files to aid in troubleshooting this problem.

    Is this a known problem with a workaround, or is M$ even trying to resolve this issue, which is happening to countless individuals trying to perform a clean installation Win 7 RC1 (and Beta build 7000)?

    Thanks in advance for any and all help!
    Brendon

    sidenote: Win7 beta & RC1 x64 installed and worked great on my old Gigabyte 8i955x Royal system w/ Pentium D (EM64T), 2gb DDR2 and 4 Raptors in Raid 10 using ICH7R controller. That system had a tri-boot configuration that was far more complex than this new system I just built. Perhaps Win7 just doesn't play nicely with certain newest pieces of hardware? I have read about many users successfully installing and using W7 x64 on very similar systems with little to no problems. I'm baffled by this!
    Thursday, May 7, 2009 7:34 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Exactly the same thing on a very similar system with W7RC. Attempted most of the fixes suggested on forums, but frankly I am not opening up a box to disconnect other drives in order to install an OS. Microsoft this is 2009: Remember Vista? It failed because it didn't play nicely with a LOT of hardware. Frankly I'm giving up on the W7RC and will be keeping XP on my home and office machines for a long time to come.
    • Edited by Correzpond Saturday, May 9, 2009 12:23 PM
    Saturday, May 9, 2009 12:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I've been having the same problem. I don't mind disconnecting my other drives but the next question is once I reconnect will I have dual boot options on startup?
    Monday, May 25, 2009 10:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Miklaing,

    No, you would have to use BCDedit or a third party tool like EasyBCD to configure the dual boot after.
    Tuesday, May 26, 2009 12:14 AM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same problem on a Dell machine with a WD 40GB drive. The install GUI sees the disk and partition, will delete, recreate and format the partition, but still get the "Setup was unable to create a system partition or locate an existing partition."  Tried using diskpart to delete, recreate and format the partition, no success.  
    The log file says "Error [-x06069d] IBS GetMachinInfo:Couldn't find info for boot disk [1]"

    None of the fixes mentioned in this thread worked.
    Friday, May 29, 2009 3:14 PM
  • Question
    Sign in to vote
    4
    Sign in to vote
    That problem seems very popular. The only cause I could find in other sources (can't confirm it, it never happened to me) that sounds plausible is this: Setup wants to install the system on a bootable harddisk and it assumes that this is the first in the BIOS. So if you have more physical HDs, change the BIOS boot order to match this request. (That is also an explanation why the "disconnect HDs and install it on one empty disk before you install others..." trick from above works.) Please report if that is a way to address the issue.
    Mob. AMD64 3000+, 1 G RAM, Mob. ATIRadeon9700, 20x DVDRW, C:XPSP3 (55G),D:WIN7 (25G),F:DATA (250G)
    Friday, May 29, 2009 4:32 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi

    I have had this issue and 2 fixes seem to solve this problem.

    Try the first and if it does not work try the second:

    1. Make sure the HDD you intend to install to is IDE 1 -- ie it comes before everything. Then in your boot order make sure it is second only to the CDROM.

    If the above does not do the trick, then:

    2. Having done step 1, load up the win xp setup and find the HDD you plan to install to. If a partition is already allocated delete it (you have to press L at some stage for this, FYI), and then create a new partition in it. Then quit XP setup and restart, and while waiting for the reboot (the 15s progress bar) swap the XP disk for the Win 7 boot DVD.

    The above trick should cover 99% of the cases.

    Ditty for any RAID setups
    • Proposed as answer by Campfreddie Wednesday, March 2, 2011 8:31 PM
    Monday, July 13, 2009 1:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I installed Win 7 RC as dual boot (64-bit XP for the earlier Win version) yesterday. Initlally the "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information." error message prevented the install to proceed. Finally, I noticed that my external USB hard drive was on and recognized by Windows Installer as an available drive. So I turned off the external hard drive and was able to install Win 7 RC in a second partiion on my primary drive (300 gb partition out of 1 tb on a western Digital Caviar green).
    Monday, July 13, 2009 3:47 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hello Everyone,  "Setup was unable to create a system partition or locate an existing system partition."  Here is how you can resolve it:

    1st  If you have multiple disk on your system you have to unplug every other disk and just leave the one you want to install win 7.
    2nd  once you took out all the other disks temporarily start your computer with the win 7 cd on the cd or dvd drive run it.  when you come to the install just install it on the right partition you want to install it  and will work if not.

    3rd go to repair option under the install then click next it will take you to recovery options just click on the dos prompt last option and then run diskpart

    4rth you should use diskpart to instraction here http://support.microsoft.com/kb/300415/ and create a primary partition should be atleast 9 GB. then exit

    5th come back and click on the X buttons to close to come back to the install and it shall work perfectly.

    initially the idea is if you take the other disks out and just leave the primary on it shall work. Hope this works for you!! let me know.
    Thursday, October 8, 2009 1:47 PM
  • Question
    Sign in to vote
    11
    Sign in to vote

    I have since successfully installed Windows 7 (in various flavors) on multiple machines, including my own! 

    The process for dealing with this error is SIMPLE:

    Unplug every EXTRA hard drive in your system, EXCEPT the one you intend to install the OS on.  (This includes extra USB flash drives that have installation drivers on them, ie., F6 setup disks) 

    If install drivers (F6 setup disk) are needed, do NOT insert usb flash drive until prompoted to do so by the Win 7 setup program.  (Windows 7 setup see this drive as another viable partition most of the time if inserted too early, and it stalls the install giving the error people reported in this thread.

    After your installation has succeeded, then go in and plug-in all other SATA, PATA, USB, and firewire HDDs.  Windows 7 will now plug & play them all without further problems!

    GREAT LUCK TO ALL.  ENJOY USING WINDOWS 7 everyone!!!

    • Proposed as answer by usnbrendon Thursday, May 6, 2010 9:03 PM
    • Marked as answer by Carey FrischMVP Thursday, December 29, 2011 3:05 AM
    Thursday, May 6, 2010 9:03 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Windows (MSFT) please provide a "advanced" option where you actually do what I say. I.e. "install Win7 on this disk", disregarding whether it is the first disk in the boot chain or not. This is embarrassing. I cannot see any issues with this since the disk is available and visible in BIOS (hey you displayed the disk as a viable target).

    Yeah, moved the target disk to the first available BOOT HD in BIOS and voila!

     

    Expanding Windows files (46%)..

    yey!

    Tuesday, January 18, 2011 6:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes it's definatly a bios issue everyone. I just experianced the same problem having just starting to create a new image and answer file for my office pc's. My text box is a DELL Optiplex 620 with multiple SATA drive attachments which I had made all active for HDD testing purposes. So I've configured a new answer file (mainly because I've set the rearm from 0 to 1 this time) and it wouldnt take! But with the BIOs adjustment and boot setting i am now cooking with gas. Thanks everyone's help here.

    Wednesday, March 2, 2011 8:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I ran into this same issue with a Dell Power Edge server.  The install repeatedly returned the response code mentioned above stating to review the log file.  No log file was created as the partition was never used at all.  Anyhow, after a number of attempts and banging my head against the wall a few too many times I checked the rear of the server and found a flash drive plugged in from someones previous troubleshooting.  Removed drive, and tried again and magic, it worked no problem. 
    Thursday, August 11, 2011 1:23 PM
  • Question
    Sign in to vote
    15
    Sign in to vote

    I had this ridiculous issue also, and found that most of the "fixes" involved removing everything USB related.  As I was trying to install via USB, that really wasn't an option.

    Eventually, I stumbled upon something that seems to be reliable and might help other people.

    Now, pay attention, because it's extremely complicated!! I mean, Windows 7 is totally confused, clearly there's something very involved going on, right?

    Well, try this insanely difficult procedure:

    after booting and selecting the language, but before clicking the "Install" button, remove the USB drive, wait a second, then reinsert it.

    Then you can proceed to the custom setup, create your partitions and Windows will create the blah-blah-blah that it needs and everything will be fine.  For me, I've tried this 5 times on two different PC's with the same USB stick, and as long as I remove the USB drive (mine is a Patriot 16GB) and then reinsert it sometime before I get to the partition creating part, everything is fine.

    Hopefully, this might help some other poor soul trying to install from USB.

    It's pretty bloody sad that this got through QA... I mean, boot off a USB pen drive?  How difficult is that to test?  And the two places I've tried it are pretty vanilla machines, nothing terribly complicated or multiple devices (1 HDD, 1 DVD) machines.  Pretty sad indeed.

    Hope this helps someone.

    CraigL


    • Proposed as answer by berserkcoder Friday, June 1, 2012 8:58 PM
    Monday, April 16, 2012 5:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This fix is perfect for the USB ones..i have absolutely banged my head over this error and at last this removing usb for a second WORKS!!

    TANX A TON DUDE ! :D

    Friday, June 1, 2012 8:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Believe it or not, this ridiculous bug made it into the RTM version of Hyper-V Server 2012. Had to put the USB drive with the drivers on it into the machine (DL585 G2) only at the Install Now message, then get the USB stick pulled out at the correct spot before selecting the drive where I wanted Hyper-V Server 2012 RTM installed.

    First I put my left foot in, then I pulled it out...and that's what it's all about. The Hyper-V Server 2012 RTM "Hokey Pokey Bug" <tm>.

    Tuesday, September 11, 2012 9:02 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Habari?

    HERE IS A SOLUTION!!

    I assume you are using a bootable usb flash drive,....after all process and you reach to the point where you want to install windows in a partition then it tells you that .....''Setup was unable to create a new system partition or locate an existing system partition.See the Setup log files for more information''...Don't worry

    what you need to do is unplug(remove) your bootable usb flash drive from your computer,then click next..after you click next it will tell you that ''Windows cannot be installed in this drive'' then plug again your bootable usb flash drive to the same usb port and click reflesh then select your patition hard drive....and click next...

    your good to go!

    Baadae!

    • Proposed as answer by Hdi_Mousavi Tuesday, July 30, 2013 1:05 AM
    Monday, December 3, 2012 8:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Xavy, 

    The above solution did not work out, tried unpluged and it gave me a new error "Windows error XXXXXXXX" , I have new hdd which is 1TB, I have disabled Optical drive / and took the CMOS Battery Out / changed the boot order. everything went in vain.... I have a wireless key board and mouse / the bootable USB .  The issue persist till now... Do you have anyother option....

    NonTechi

    Monday, January 7, 2013 9:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey guys, I found the answer to your problems after giving up a few videos that I had on a particular partition.  The problems with Windows 7 is that it needs there to be an unallocated space of about 120Mbs.  Solution, don't use all the space on the disk.  Delete your target partition and recreate it leaving about 120MBs unallocated and try again.  I did that and it worked.

    • Proposed as answer by ThePatriot1 Friday, January 18, 2013 5:19 PM
    Friday, January 18, 2013 5:19 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Another reason - the HDD is not the first boot device in BIOS.
    Friday, June 28, 2013 7:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's a weird one. I have tried pretty much everything mentioned here, but then I was messing about with setup and disabled the check for signed drivers. Bang! Installed. I have no idea why this helped, but since I also had problems finding drivers I thought I would try to fix that problem first, and instead the problem never reared its ugly head again.

    One reason it's weird is that I have virtually no valid drivers. My network cards aren't recognised, except for the bluetooth, but at least I am in. The rest I can probably manage.


    • Edited by Rouffian Tuesday, July 9, 2013 11:39 AM More info
    Tuesday, July 9, 2013 11:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey i have a solution for this.

    if you have 2 hardisk you just unmount or remove your  second hardisk.

    thats work for me.

    • Proposed as answer by diazadhitia Friday, July 19, 2013 8:26 PM
    Friday, July 19, 2013 8:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi xavy The above solution work out. Thank you very very much! Hadi
    Tuesday, July 30, 2013 1:12 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi xavy, The above solution worked for me. Tanx very very much. The good idea! :)
    Tuesday, July 30, 2013 1:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks very much for this.  Was trying to do a clean install of Windows 7 to upgrade to 64 bits and couldn't figure out what was going on.  Read this and did some looking.  Sure enough, one of the kids had a USB in the back of the computer.  Removed it, restarted, no problems.  Thanks!
    Sunday, August 11, 2013 12:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just in case someone out there in the interwebs is having a similiar issue...I spent a long time until I finally figured out it was my USB key was 3.0, which apparently Windows installation doesn't like. It was very mystifying but switching to USB 2.0 solved the problem!
    Thursday, August 29, 2013 1:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you very much sir,

    today i learned a new lesson also. i was installing by using USB media. but until today i dosen't find any any problem. this was the first issue.

    THANKS AGAIN.

    Sunday, September 8, 2013 1:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks A lot ..

    its very simple solution :)

    Tuesday, September 24, 2013 8:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Using a 2.0 usb rather than a 3.0 usb worked for me.

    Thanks.

    Monday, October 7, 2013 11:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    thanks dude. I was stressing out over this so much
    Saturday, November 23, 2013 7:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I just stumbled across this post after researching my own particular experience of this error.
    Using an external  virtual cdrom drive I thought there lied the problem.

    It was an older laptop I was reconditioning and after checking the bios I discovered the date and time was out.
    As soon as I corrected it and rebooted setup was happy to install to a full 160gb hard drive with no reduced partition.

    Thursday, November 28, 2013 9:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My problem was pretty similar to yours. I have a lenovo x61 tablet, on which I wanted to reinstall a clean win7.

    After deleting the old one, I got the error: setup was unable to create a new system partition...

    I was using a 4gb Data Traveler from Kingston created with the Universal USB installer and a windows 7 iso created by others that worked in the past. 

    I have just began the installation of windows 7 after 3 days of errors. It finally worked, but with none of the solutions from above.

    What worked for me, was to create  another Windows 7 USB flash drive with the same ISO and using the tool from Microsoft - Windows 7 USB-DVD Download Tool. I used a no name 8gb flash drive which somehow worked...

    I know it's not a systematic solution, but this worked for me when no other would work.

    ClaudiuA

    Friday, January 3, 2014 11:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I found another solution

    The problem was the because I used a usb 3.0 flash drive In a usb 2.0 PORT.

    If you installed tthe windows iso on a 3.0 thumb drive you need to boot it up from a 3.0 port on the computer or it will give that error.

    If you don't have a 3.0 port you need to reburn the I so on a 2.0 thumb drive

    I Used Rufus to burn iso to thumb drive.

    Sunday, January 5, 2014 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just had this happen to me last night on Server 2012 R2.

    I have a Revo x2 PCIe drive and ran server 2008 and server 2012 for years without errors.

    When I tried to do a reinstall, the installer threw that "can't find a partition" message and I noticed that the standard 300MB boot/system partition wasn't being created. 

    It turns out, the REVO drive for some reason, decided to drop the RAID-0 striped drives but didn't report it during the system POST. I just deleted the set, recreated the RAID-0 stripe and the Windows Server installer was able to function.

    I guess Windows want's to make sure your drives are configured and running optimally before it even lets you run the Partition Manager.

    Windows caused an invalid page fault in module 00x0000FFFF,..Please install linux to fix this.




    • Edited by GHynson Friday, February 7, 2014 10:17 PM
    Friday, February 7, 2014 8:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Genius - solved my problem with installing Windows 7 from USB - just remove the install flash drive for a second after you select the language but before you hit 'Install now'

    Thanks a bunch!

     
    Tuesday, February 11, 2014 10:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm embarrassed to say that I spent hours trying to figure this out and looking all over the internet.  This seems like it should be so simple!  I know the answer to this has been stated but I just want to reiterate.  I was having the same problem, I would install my drivers, take out the usb flash drive, click refresh and kept getting the error.  It worked for me when I restarted the computer without the flash drive connected.  I did not connect the flash drive until it asks you to insert the media with your drivers.  Insert the drive, browse, install the drivers, remove the flash drive, refresh, and it worked.  I tried this so many times (the wrong way) that when it finally worked I gave out a nice big FU to the computer. lol.  Thanks guys for all of your help!
    Sunday, February 23, 2014 2:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey !!!

    I had the same issue installing from USB i did none of the other guys fixes 

    I got windows install started (from USB Stick) then as it got to partitioning i "removed the memory stick" and let windows format and create system partition then just slipped the USB stick back in and after 2 days of trying all sorts i finally got windows to install

    Thats it really 

    PS i have installed windows like tons of times and never came across this issue before 
    • Edited by Ash Cook Monday, March 31, 2014 11:18 AM
    Monday, March 31, 2014 11:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this ridiculous issue also, and found that most of the "fixes" involved removing everything USB related.  As I was trying to install via USB, that really wasn't an option.

    Eventually, I stumbled upon something that seems to be reliable and might help other people.

    Now, pay attention, because it's extremely complicated!! I mean, Windows 7 is totally confused, clearly there's something very involved going on, right?

    Well, try this insanely difficult procedure:

    after booting and selecting the language, but before clicking the "Install" button, remove the USB drive, wait a second, then reinsert it.

    Then you can proceed to the custom setup, create your partitions and Windows will create the blah-blah-blah that it needs and everything will be fine.  For me, I've tried this 5 times on two different PC's with the same USB stick, and as long as I remove the USB drive (mine is a Patriot 16GB) and then reinsert it sometime before I get to the partition creating part, everything is fine.

    Hopefully, this might help some other poor soul trying to install from USB.

    It's pretty bloody sad that this got through QA... I mean, boot off a USB pen drive?  How difficult is that to test?  And the two places I've tried it are pretty vanilla machines, nothing terribly complicated or multiple devices (1 HDD, 1 DVD) machines.  Pretty sad indeed.

    Hope this helps someone.

    CraigL

    You are the man! Hours of beating my head against the wall and then I run across your comment! You sir, are a genius!



    • Edited by qopiyu Monday, March 31, 2014 8:00 PM
    Monday, March 31, 2014 7:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Alex,

    Your colleague is likely to be correct. Removing data and power cables from everything but the disk you intend to install to should force the installer to partition, format and set it as active and allow your install to succeed. You can also move the drive you want to install to to the first position on the HDD bus for a similar result.

    If you have AHCI enabled in your BIOS, you may get a BSOD on booting the new install - disable AHCI and you should be good to go.

    Good luck.
    Andy.

    I had the same issue Removing USB drives and external mouse did not help (HP EliteBook 9470m). However after reading this post, I removed the Network and Power and tried again and it worked as it should. I had to re-insert the USB drive to continue with the imaging process.

    Thanks for the help fellas!

    C0W

    Tuesday, April 8, 2014 11:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Its SIMPLE am an I.T Specialist for 7yrs. I have dealt with this in a very SIMPLE way. Just go to the BIOS and change the SATA-MODE from AHCI to IDE. And Viola THIS WORKED...!!! BELIEVE ME
    Friday, April 18, 2014 4:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank You so much!!!! i spent days trying to figure this out. I dont know why i didnt think of unplugging the second hard drive with linux on it.
    • Proposed as answer by RichieSil Wednesday, May 7, 2014 9:47 PM
    Wednesday, May 7, 2014 9:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this ridiculous issue also, and found that most of the "fixes" involved removing everything USB related.  As I was trying to install via USB, that really wasn't an option.

    Eventually, I stumbled upon something that seems to be reliable and might help other people.

    Now, pay attention, because it's extremely complicated!! I mean, Windows 7 is totally confused, clearly there's something very involved going on, right?

    Well, try this insanely difficult procedure:

    after booting and selecting the language, but before clicking the "Install" button, remove the USB drive, wait a second, then reinsert it.

    Then you can proceed to the custom setup, create your partitions and Windows will create the blah-blah-blah that it needs and everything will be fine.  For me, I've tried this 5 times on two different PC's with the same USB stick, and as long as I remove the USB drive (mine is a Patriot 16GB) and then reinsert it sometime before I get to the partition creating part, everything is fine.

    Hopefully, this might help some other poor soul trying to install from USB.

    It's pretty bloody sad that this got through QA... I mean, boot off a USB pen drive?  How difficult is that to test?  And the two places I've tried it are pretty vanilla machines, nothing terribly complicated or multiple devices (1 HDD, 1 DVD) machines.  Pretty sad indeed.

    Hope this helps someone.

    CraigL


    I can't believe THIS worked! 

    Holy mother of God! 

    Thanks a million!!!!


    Thursday, June 12, 2014 10:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    thank you very much man your a life saver i spent all night trying to find what was wrong with my hard drive
    Thursday, June 19, 2014 1:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    SOLUTION:

    I solved the issue by putting a Lenovo Thinkpad T540p on it's docking station USB 3.0 and it suddenly worked.

    Previously, I would get this error when plugging a San Disk Cruzer Extreme in any USB2.0\3.0 port.


    Tuesday, June 24, 2014 5:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you,

    This resolved my issue, I was trying to install Windows Server 2008 and encountered the "setup was unable to create a new system partition" message, I shut down the server and removed the RAID Controller only leaving the HDD required for the OS.

    Thursday, June 26, 2014 10:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    un-bloody-believable

    Thankyou for sharing that CraigL, I cannot believe that works! I have been racking my brains over this for 3 hours now!

    wow. just.... wow

    Saturday, July 26, 2014 6:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's easy I been through lot of those All will tell u to unplug all USB and stuff only thing you need to do is go to setup screen to HDD part and delete formate partition and then unplug USB flash drive you trying to install windows from then click next or install and replug USB flash drive to start installation works like charm no problem what so ever
    Wednesday, August 6, 2014 1:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    CraigL,

         You were absolutely right.  I only had a single SSD + the USB install media in the system. Unplugging the USB install media ( stick ) before clicking Install did the trick.  This problem still exists with the post SP1 install media.  

    Thanks,

    J

    Sunday, August 10, 2014 12:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    this worked for me.
    Monday, August 18, 2014 1:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you!  This worked for me.  After messing around for an hour, the solution was as simple as pulling out a flash drive that was still inserted in the rear of the pc.  

    Much frustration averted! 

    Many thanks!

    Friday, September 5, 2014 11:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello everyone,

    I am not advanced tech, I just dabble. I have been fighting this same problem for 4 days. I am installing a clean win7 64bit to a pair of raid 0 SSD's I just bolted into an existing system. I am installing win7 from the original DVD. First you must have the raid drivers for your motherboard. OK got that, and still the same error. seems this is a generic error message for a number of different issues. Many of the fixes are listed elsewhere on this page (thanx to all of those contributors). In my case the fix was bios related. The win7 installer wants the drives it lists to install to too be listed in the bios in the same order as the installer lists them as. With this done it was not necessary to open the case and unplug other drives. My Asus bios is set for RAID and the array was built in the raid configuration utility at boot. I hope this helps someone. Thanx for reading.

    Tuesday, September 16, 2014 12:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If possible, try to boot system from Windows 7 using an EXTERNAL DVD ROM. I have tried it and it worked successfully on my Acer Laptop.
    Tuesday, September 23, 2014 6:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If possible, try to boot system from Windows 7 using an EXTERNAL DVD ROM. I have tried it and it worked successfully on my Acer Laptop.
    Tuesday, September 23, 2014 6:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank You so much. It really helped.

    Tuesday, November 25, 2014 10:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    THANK YOU!!!!  So here I am 7 years later installing an old Windows 7 CD on an even older Compaq with system similar to yours (except 4 GB RAM) and having the exact same problem as you did. I had installed Linux on this system since then and an extra (bigger) disk drive from a newer PC (motherboard had literally fried) to recover some photos, etc. So, here I am with two SSD drives installed in the tower and trying everything imaginable (like you) to get windows to load, and I stumble across this post. Opened the tower, unplugged the Linux disk, booted to the CD and now Windows installing beautifully :) Thanks again (7 years later)!
    Monday, May 8, 2017 4:59 PM