Windows 10: Both USB and DVD installer hang at initial splash

yesterday I downloaded the 10041 ISO from the Windows 10 Technical Preview ISO March Update - Microsoft Windows

I installed by mounting the ISO into a VirtualBox and enjoyed having a look around. In fact I like it so much at my initial impression I decided to move into a dual boot system.

I have a 250gb SSD as my C: drive so I partitioned it and created a D: of 80GB for the Windows 10 preview.

I then tried creating 2 different USB installers... one Rufus MBR for legacy BIOS... and the second using the microsoft USB/DVD installer tool. I also burnt a DVD.

In all cases I used the very same ISO that I mounted sucessfully inside the VirtualBox yesterday.

Each one of the 3 installers I created seemingly hangs at the initial black splash screen with the 4 blue windows in the centre. It goes no further and believe me I waited 20 minutes on one of them.

BTW.... I tried opening the ISO in WINISO and then mounting to BD ROM drive. Then selected the setup.exe and away it goes just like setting up on the VBox ... but then it get to a screen which suggests I need to install a different language pack to the one already installed, so I immediately realised this route is trying to upgrade my Win 7 which I don't want... so I aborted.

Anyone got any ideas please....?

Nick

:)

 

Saitek Eclipse III drivers for Windows 10

Hi.

Their website doesn't have any drivers for the keyboard anymore, so can't even try to do that.

I will email them and ask if they have the old ones still, but failing that do you have any ideas?

I'm also trying to do a clean install of Windows 10 on a new hard drive, but it just hangs on the initial windows 10 splash screen logo before the install begins, any ideas?

I will try doing it from dvd rather than usb, unless you have a different potential solution?

Thanks.

 

Clean Windows 10 Install Hangs on Initial Splash Screen

I'm in the process of resurrecting some "old" hardware. It was running Windows XP effectively as recently as a couple months ago. In trying to build this second workstation for light duty work, I purchased a SSD and a fresh copy of Windows 10.

When I boot from the install media (provided DVD) it pulls up an initial black screen with blue Windows (10) logo. That's it. No spinning circle. Nothing else. I've noticed that the keyboard is responsive to toggling Num/Caps Locks for the first minute
or two while the DVD is still spinning, but the DVD spools down to a crawl and the keyboard then becomes unresponsive to Num/Caps Lock toggle attempts. A PS2 keyboard did work notably longer than its USB counterpart, but did eventually lock up.

I let it sit on that black screen for as long as 4 hours, with no signs of anything happening. I also tried creating a bootable USB and ran into the same problems as with the DVD install media.

In an effort to troubleshoot, I dropped my mobo down to one GPU, and stripped everything unnecessary off the motherboard.

Things I've tried:

- Different keyboards, both USB and PS2

- Different mice, both USB and PS2

- Different GPU's

- Different RAM combinations

About the only constants have been the CPU, mobo, and PSU (which should be fine; it was replaced relatively recently and is a higher end modular Corsair PSU).

At this point, about the only thing I can think to do is sysprep the install on another machine, but since it's an OEM OS I anticipate having to reach out to support to get it activated the second time anyway. I'm also nervous about sysprepping it on my
other workstation, as I'm running a hardware-based RAID setup and I admittedly don't know enough about it to know if I could compromise my RAID setup when I throw on another primary SSD for the sake of installing the OS. It's my primary development workstation
and I can't risk any downtime on that machine.

Does anyone have an idea what else I could try to get this installed? Seems ridiculous to pay $140 for a piece of software that I've had to mess with for over 2 days, and there's still no light at the end of the tunnel. I've lost about $1200 in productivity
because of this issue so far... really getting desperate and irritated at this point. HELP!

Hardware:

4 Ghz quad core AMD, 64 bit

Asus mobo running two GPU's in SLI

4 GB RAM

250 GB Samsung SSD

Background:

I'm primarily a web developer (HTML, CSS, php, etc) but have done a fair amount of light IT work at day jobs over the years. I've also assembled many PC's over the years, and have successfully installed Windows on several dozen machines in the past.

 

Please update your SF Systems Specs with complete information.

• In the System Manufacturer/Model Number field, manually type Desktop or Laptop adding it to the information already in the field.
  The specific model number is important - there are often many models of a given series. For example, my machine is a HP Pavilion dv6, but there are tens of the dv6 series, so dv6-6c10us is the specific model.
  
  
• Specify Custom Build as the manufacturer if it is not an OEM machine.

The easiest way to do this is to use the information from a PUBLISHED Speccy report.
See: http://www.sevenforums.com/tutorials...tem-specs.html

Post the link to the report that Speccy gives you and after you submit the post, open the Speccy link. You can then put the windows side-by-side and simply copy the information from the Speccy report to your System Specs.

Click here to view your system specs on SevenForums.

Click on My System Specs in the lower left of any post by any member to see what is presented about their machine.
Armed with the system information, I can suggest further actions, such as BIOS updates. But I know noshing about your machine other than it's a Samsung laptop running Win7 x64.

If you have it, p[lease post the support page for your machine, OEMs often put this information in a Start menu group or in IE favorites. This will save me from having to look it up and ask if I found the correct page.

Thanks,

Bill
.

 

http://speccy.piriform.com/results/odZwpMI0Tq2j4RbDrIemUSC

And info updated

 

Thanks for updating the information, here's what I found ...

Machine Ref: NP-RV511E (NP-RV511-S01UK) | Support | SAMSUNG UK

Samsung support is interesting ... I can't really figure out what versions are available because they use updater software.
The date of your BIOS (from Speccy) looks about right for that machine though. I was hoping that might be the snag, but I'm not sure now.

Lots of XP and Vista references on the support page, was this machine upgraded to Win7?

At the bottom of the support page is this little tidbit: SW Update
Using the SW Update function, you can easily download and install Windows 8 device drivers and software.

How it might be useful, I'm not sure yet. Since your base machine is Win7, don't update the drivers to Win8 yet - maybe after Win10 gets installed, but Win10 should carry all of that with it.

It worked in Virtual Box because the hardware is emulated.

Try this, see if your machine is 8.1 ready (Win10 has the same requirements)
Upgrade Assistant: FAQ - Windows Help

 

I'm also not terribly impressed with the info on the samsung support page for my model and what looks like duplication of drivers.

The Windows 7 x64 came preinstalled on this laptop.

BIOS was updated by me in 2012 when the 1.0.0.2 version was released for this machine and device drivers are always regularly updated. The Nvidia driver updates are always notified when available and I always install.

Tried the 8.1 upgrade assistant as you suggested and ran it on this laptop and it has no problem with selling me the 8.1 OS after checking compatibility.

BTW.... I tried the following tho just realised windows defender was still on and I only turned off Kaspersky instead of uninstalling it.
so I'll do it once again and make sure all the following is done exactly.

What you can do before attempting the upgrade?You can do some pre-requisite tasks to ensure a smooth migration to Windows 10. If you are using a name brand computer such as a Dell or HP, go to the manufacturers website for the model computer you are using and download the latest available drivers for that computer. Store them on a disc or USB thumb drive. Important drivers you should try to obtain include Chipset, Network and Video Drivers. Its possible that they might have only Windows 7 drivers, those will work with Windows 10.
Other things you can do:

• Uninstall any security software before attempting to upgrade.
• Disable any encryption software you might have installed.
• Disable/uninstall disk utility software such as DVD/CD burning utilities or third party defragment programs such as Perfect Disk.
• Make sure your computer is updated (devices and applications).
• Disconnect any external devices before installing.
• Check your hard disk for any errors:
  - Click Start
  - Type: CMD
  - Right click CMD then click Run as administrator
  At the Command Prompt, type: chkdsk /r /f
  Exit the command prompt.
  When you restart your system, your computer will be scanned for errors and attempts will be made to correct them.
• Another thing you can do is disable Start items:

• Click Start
• Type: MSCONFIG.
• Hit Enter on your keyboard
• On the General tab, click Selective Startup.
• Under Selective Startup, click to clear the Load Startup Items check box.
• Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
• Click OK.
• When you are prompted, click Restart.
• After the computer starts, check whether the problem is resolved.

Run the System File Checker utility.
SFC/Scannow checks your Windows installation for errors and corrects them. This will help with ensuring that a smooth upgrade occurs.
Click Start
Type: CMD, from the results, right click CMD
Click ‘Run as Administrator’

 

Thanks for the Win7 information (pre-installed on your box, not upgraded from XP or Vista).

Sounds as though you're on top of things - that's always good! Some machines have software/drivers that are severely back level.

I usually discount AV software, and I also forget to ask about encryption. So that's a good checklist.

I took another look at your Speccy - I just re-read post#1 and wonder about the BD ROM software, Daemon tools has been know to cause issues on some machines, but I didn't see it - might have missed it.

What I did see is a few scheduled tasks that might...might be part of the issue:
Scheduler
Adobe Flash Player Updater
GoogleUpdateTaskMachineUA
GoogleUpdateTaskUserS-1-5-21-3687321098-2695874198-1787335006-1000UA
FacebookUpdateTaskUserS-1-5-21-3687321098-2695874198-1787335006-1000Core
FacebookUpdateTaskUserS-1-5-21-3687321098-2695874198-1787335006-1000UA
GoogleUpdateTaskMachineCore
GoogleUpdateTaskUserS-1-5-21-3687321098-2695874198-1787335006-1000Core
** ASC8_PerformanceMonitor
** ASC8_SkipUac_BASE-1268
** Driver Booster SkipUAC (BASE-1268)
** Driver Booster Update
SamsungMagician
SmartDefrag4_Startup
SmartDefrag4_Update
Uninstaller_SkipUac_Administrator
Uninstaller_SkipUac_BASE-1268

Please disable the tasks above, for test purposes.

I'd rather see them uninstalled, particularly the Advanced System Care pkg. I understand if you want to avoid doing that, but ASC is also know to cause issues on some machines.

The other thing I saw was Media Center extensions - this shouldn't cause an issue, but if you don't use Media Center, consider turning it off in Programs & Features -> Turn on or off Windows Features.

You could try disconnecting all external devices while you attempt an install. Use the laptop KB and touchpad.

The only other thing I want to look at is the NVidia driver - again, it doesn't seem to be out of range, but Win10 is moving to DirectX 12 and ... I'm not sure if the mobile GPU is interfering, so I need to do some research.

Lots of I don't knows - everything looks right and you're doing the right things. This becomes a process of elimination and that's the right approach. Get to a base and move up until it 'breaks' - then you know what 'breaks' it.

 

So...... if i do a completely clean install onto a brand new SSD there is nothing that can cause conflict because the laptop has no system whatsoever and I tried that first.

I removed the access cover and removed the Crucial 250GB with my Windows 7 system on it and inserted a brand new Samsung 850 Evo 250GB.

Then plugged in only the Rufus USB installer and finally went to the BIOS to change boot priority to the USB.

The Win 10 logo screen that comes up doesn't have the circle of clockwise spinning dots to indicate it's running and it just sits there refusing to do anything.

By way of elimination that would suggest it has to be something in the machine..... or the thumb drive.... so I burned to a DVD but the same problem.

When I put the Win 7 drive back in and used WINISO to mount the ISO to the BD ROM drive and execute the setup file it goes through all the initial updating and checking compatibility screens and looks like it will work.... but eventually it reaches the WIN 10 logo screen and again it stops right there.

Surely there has to be a conflict with the installation instruction set and my laptop...?

How can I run a logfile during the process to see which instruction is stopping it...?

 

Also, if there are any things you can disable in the BIOS which aren't necessary to the install, you might try disabling them. I seem to remember over on eightforums, someone had a DELL laptop which would only let Windows 8 install once they'd disabled a built-in Bluetooth device.

Edit: Another thought - does an earlier version of Windows install?

I think you can still get Build 9926 from here, although I'm not sure how long that will stay there, so that might be worth a go.

You could also try Windows 8 .1, I guess
Full version here
http://windows.microsoft.com/en-GB/w...-refresh-media
and trial version of Enterprise here
https://technet.microsoft.com/en-gb/.../hh699156.aspx
I guess you won't have a product key so won't be able to go ahead with the install of the full version, but it might prove something if it even gets that far.

 

Thanks for the tip David.... of course I'd need to know exactly what is required to be enabled within the BIOS so I can try to disable the rest..??

I downloaded the earlier version ISO but it's the same story.

I also ran the Windows 8 compatibility upgrade assistant and got the green light to buy 8.1 from MS but only if I didn't expect to retain settings and apps.... personal data only as 6 of the programs I have flagged up as needing re-installation..... but as Bill suggested it was a good way of identifying that my machine has the compatible hardware for Windows 8.

I have a Linux Gparted boot DVD with access to lots of utilities that run in the Linux environment...

Does anyone know the commands to mount the Win 10 ISO from a CMD prompt to execute the 'setup' file from within the file structure as it will automatically log the process and we can then see where exactly it's stopping by logging the error...? This may just point to what might be preventing the install....?

EDIT:.... I'm going to try installing Windows 8.1 Pro onto a clean SSD and see what happens... *Huh

Edit 2.... So... 8.1 Pro is installed on a new SSD and I'm using it now... currently downloading 1.13GB of Samsung drivers for Windows 8 and will then sift thru and install the important ones... plan is I will then attempt to install the Win 10.041 TP on the other partition I prepared on this SSD and hopefully with zero conflicting 3rd party software and the correct drivers etc for win 8 I might get lucky... lets see...*Wink

I have a SATA extension cable on he way and the plan has always been that I can then just swap out my everyday Win 7 drive with this new one without having to open the laptop every time.

 

I have to admit that I'm stumped. Post# 7 is pretty much the cleanest install possible, if I read it correctly.

I just want to be certain that you're booting from the install media (Thumbdrive or DVD) and not installing from inside Windows. The clean SSD basically answers that question, but the WINISO / BD ROM paragraph makes me question my own sanity. I'm pretty sure that you're saying that just to show how far the install gets compared to a booted install (or a VM install - which does complete successfully)

It's a laptop, so there aren't a whole lot of components that might be installed and need to be removed to test. As long as every external device was NOT connected, I think you've done your due diligence.

Here's a few TechNet articles that might get you started, they are very technical, but there might be something you can use in one or more of them to get past the issue. I was looking for a way to turn off device driver installation (use the base MS drivers), but I couldn't find a simple switch (i.e setup /disableDriverInstall). I'm sure there's a way to control that, but is it worth the time and effort to find the install stage and create a script to override it? That will be your decision - try to solve this or run Win10 in a VM until there is a release closer to RTM.
Windows Setup Configuration Passes
Windows Setup Log Files and Event Logs
Deployment Troubleshooting and Log Files
Windows Deployment with the Windows ADK

The above is a lot of reading and a lot of testing. Your call on the way forward.

I haven't read the pages entirely, but you seem fairly savvy. See what you can glean from them and ask some questions, I'll try to answer what I can (of course, I'll have to read the article more in full). There isn't any way for me to test what you have, so I'll probably punt on most of the answers. Other members have more experience in Windows deployment and they might stop by and offer you their suggestions.

The difficulty I see is that the install doesn't complete, so will the logs be retained or does Windowes setup roll everything back. I think the logs will be there, but you'll have to boot back into Win7 and connect the SSD externally.

This is some project - makes things interesting *Wink

One shot in the dark - try the 32 bit ISO. Can't imagine how that would succeed, but hey .... who knows.
If it turns out to be the NVidia GPU, there isn't anything you can do until MS updates it's driver package. A clean install booted from media to a clean SSD (it is unallocated - right?) has no knowledge of the hardware drivers until Windows gets to that section of the install (keeping in mind that hardware is mostly emulated in a VM).
Please report feedback to MS through the Insider forum - there might be someone that knows Samsung issues.
Windows Insider Program - Microsoft Community

I'm stumped!

Bill
.

 

Edit 2.... So... 8.1 Pro is installed on a new SSD and I'm using it now... currently downloading 1.13GB of Samsung drivers for Windows 8 and will then sift thru and install the important ones... plan is I will then attempt to install the Win 10.041 TP on the other partition I prepared on this SSD and hopefully with zero conflicting 3rd party software and the correct drivers etc for win 8 I might get lucky... lets see... *Wink

hope this improves your success - Win8.1 installs - great!

 

Hey Bill

That's what I thought.... hence why it was my first choice.... at least it's perplexing and as such more than average to solve.

Anyway... by process of elimination we now know my hardware is perfectly capable of running Win 10 as I'm writing this from IE 11 browser on Win 8.1 Pro. The documentation for Win 10 states that it has exactly the same system requirements as Win 8.

I'm now using 8.1 Pro (clean install to clean SSD worked perfectly first time with a Rufus USB installer) and downloaded all the x64 drivers from the Samsung support and installed all Win 8 drivers for this machine. Of course there are no other 3rd party apps installed.... just windows 8.1 plain and simple.

Oddly Samsung supplies 2 different drivers for Bluetooth, WLAN and Touchpad (all 64 bit) ... is it normal to have more than one driver for a device...?

Anyway I'm now downloading 51 updates (965mb) for Windows 8.1 pro and once they're installed I should be set to try and upgrade to Windows 10.041 TP, but I'll try the ISO first, tho rather than boot from the installer I'll execute the setup file by exploring the USB drive. I see there are actually 2 different size setup files, one is in the root folder and the other is inside the 'sources' folder and both take a different route to installation.

I think I'll be an installation expert after this.... *Cool

Nick

 

I thought this was worth copying over from Andre Da Costa on the MS page in answer to same question over there. I can only assume his MS loyalty is why he might suggest Rufus is a factor...? But interestingly I went with NTFS format which Rufus automatically selects so about to give the FAT 32 a try.... it kinda makes sense that the installer was failing at the very first screen and that it could be a format issue.

I suspect Rufus might be a factor in why the installation is not working from the USB thumbdrive.
Format the thumbdrive as FAT 32
Download and Prepare Windows 10 Preview .ISO file (build 10041)There are a number of ways to start the Windows 10 setup, but before we even do that though, we need to ensure we have our copy of Windows 10 downloaded and turned into a bootable copy.
Download: Windows 10 10041 English: x86 | x64 | More versions
Additional languages can be found here:
http://windows.microsoft.com/en-us/windows/preview-iso-update?os=win10
Determine whether 64 bit or 32 bit is right for your needs:
The following article will help determine the difference between both:
32 vs 64 bit
http://windows.microsoft.com/en-US/windows7/32-bit-and-64-bit-Windows-frequently-asked-questions
The article references Windows 7, but the same principles apply to Windows 10.
Preparing the .ISO file for installation.
See instructions for burning .ISO files in Windows 7 or later:
http://windows.microsoft.com/en-US/windows7/Burn-a-CD-or-DVD-from-an-ISO-file
You can also use the Microsoft USB/DVD Tool, which is recommended for Windows XP users.
After obtaining the .iso file you use the Microsoft .iso to USB/DVD tool to create a bootable DVD or USB (requires a blank DVD or USB flash stick of at least 4 GB).



Try installing again.