White screen during install relating to network/internet?

[themightymrp]

Hi all

 

I've come across an interesting one. When installing Windows 10 (any version) on an Acer Aspire ES1-512, if I have an Ethernet cable plugged in then on the first reboot I get a pure white screen (solid) with a black outline rectangle in the upper left corner. The install seems to stick at this point. If I disconnect the Ethernet and reboot, the install continues without issue.

 

Interestingly, if I press Alt+F4 at the white screen it disappears and I get the blue background with white writing saying something like "setting up" and the spinning circle animation. This lasts for a couple of seconds before the white screen comes back.

 

I've got 2 thoughts on this - a network driver it REALLY doesn't like, OR it is trying to connect to a URL/site for some reason during install.

 

Can anybody shed any light? Or has anyone seen this?

 

Cheers

 

EDIT - I should mention I am installing from an unmodified ISO burnt to DVD which was downloaded from the VLSC

[Garacesh]

VLSC ISO's are preconfigured to search for a KMS, so I can't imagine it's trying to connect to the internet? Product key is the only reason I'd suspect it would be going out..

 

If it's only on the Acer and nothing else, then it's likely to not be image related. Does it happen on other hardware?

You've not got driver installs that are less "Install a driver" and more "Download the latest driver from $Site" have you?

[themightymrp]

So far I've only had the issue on the Acer, but then I've only tried 3 different laptops. Still you'd think that was a good indicator of it being something to do with the laptop! There's no kind of deploy/inject driver stage at all at the moment. I'm purely installing Windows from the burned ISO without any changes. I'm wondering if its a dodgy net card now.

 

Thanks for replying

[Garacesh]

Oh, bummer, I completely missed the 'burned' bit. My bad!

 

Maybe it is trying to authorise your key but it can't? (Which could be network related, if it can't reach your KMS/Their MAK servers) and you're supposed to be getting a 'Dun't work. Gief new key' popup.

[themightymrp]

Possibly I suppose. I shall see if I can investigate that

[themightymrp]

Tried a few different installs with and without a network cable plugged in, on various laptops. Its only the Acer with the issue

 

Must be a dodgy network card driver (or the card itself is duff)

[clareq]

I get the same issue on a hyper-v VM. Your fix of disconnecting the network works. It obviously isn't the network card, as other VMs work fine.

[Garacesh]

I haven't seen the issue, but I've only tried on 1 PC and 1 tablet so far. I do have other hardware to test on, though, once I've gotten driver deployment working fully as part of the WDS imaging. I'll report back if I end up with a similar issue.

[themightymrp]

Ahhhh ok then. Now more confused. Would love to know whats causing it - my Hyper-V install using my same installation disk has no issues.

 

Do you get the white screen then?

[clareq]

Yes, exactly as you describe. Occasionally I get it during initial install, at other times I can finish my install, create my fat image, sysprep and capture said image and I get the white screen when running the OOBE on the original VM after sysprep.

[themightymrp]

Well at least I'm not alone I'd love to know what is causing it, especially as you are getting it after you've sysprepped the image :-/