Original Title: Problems installing Windows 10 on Dell Latitude E6420I have tried numerous times to install Win 10 on this computer both from the ISO and the upgrade. It all goes well until it restarts, and initially it shows the Windows icon and then the screen goes blank and stays that way. I have to do a hard restartand when Win 7 comes up it has an error message OxC1900101-0x20017 the installation failed in the SAFEOS phase during boot operation. I have tried everything I could find on the internet such as uninstalling AV, disabling wireless and bluetooth, etc. Is there anyone that has successfully installed Win 10 on this model of laptop or knows a way to get past this error? It would be much appreciated.
Hi,Thank you for posting your query on Microsoft Community.I understand that you are facing issues with Windows 7. I apologize for the inconvenience caused to you.The issue could occur if there is change in Windows update settings.Refer to the below methods and check if it helps.Method 1: I suggest you to perform the Windows Update troubleshooter and Background Intelligent Transfer Services. Check if it helps.1. Tap on Windows Key and click on Search bar.2. Type “ Troubleshooting” without the quotes and click onTroubleshooting.3. Then click on View All on the left panel of the screen.4. Click on Windows Update and Background Intelligent Transfer Services.5.
Click on Next and follow the prompts to run the troubleshooter.If the issue still persist, refer to the below method.Method 2: I suggest you to try to start Windows Installer services and Windows Update services. Check if it helps.1. Press Windows Key + R Key.2. Type ' services.msc' without the quotes and click on it.3. Search for Windows installer.4. Double click on it and under Startup type, selectAutomatic.5. Then click on Start button.Note: If you are not able to change the Startup type, then continue starting the service by clicking on Start button.Reply to us with the information, so that we can assist you better.Let us know if you need any further assistance on Windows related issues and we will be glad to help.
I know this is very late, but what I have found is that to get rid of all the driver bangs on the Latitude 10 ST2 you also have to install 4 other things. The driver cab from Dell will get you most of the drivers you need.
What I have done is assign a mandatoryapp (bundle of 4 apps) to Latitude 10 ST2s that install these 4 things.The first app I install is the Intel Clovertrail UMA Graphic Driver. Quiet install command: Setup.exe -s -nrThe second app I install is the Broadcom Bluetooth package. Quiet install command: btnetwork.exe /sThe third app i install is the Broadcom GPS package. Quiet install command: msiexec /i GPSBCM4751.msi /quiet /norestartAnd the fourth app is actually a Windows update; it installs the Intel DMA drivers. Quiet install command: wusa Windows8-RT-KB2756872-x86.msu /quiet /norestartThis has been working for me ever since the Latitude 10 ST2s came out. The issue I have now is with Windows 8.1.
MDT2013 deploying 8.1 just locks up the Latitude 10 ST2. After Postinstall restarts, it just sits at a blank black screen.This occurs on new installs or refreshes. But if I do a manual upgrade to 8.1, no problems. The good thing about MDT2013 though is that you can leave Secure Boot enabled in the BIOS. I'm having the same lock up issue on the Latitude 10 with MDT 2013. Did you ever figure this out?Sorry I haven't responded back to your question sooner. But the answer is no.
I stopped working on it for a while and just started to readdress it again. I'm having the same lock up issue on the Latitude 10 with MDT 2013. Did you ever figure this out?Sorry I haven't responded back to your question sooner. But the answer is no.
I stopped working on it for a while and just started to readdress it again. I'm having the same lock up issue on the Latitude 10 with MDT 2013. Did you ever figure this out?Sorry I haven't responded back to your question sooner. But the answer is no. I stopped working on it for a while and just started to readdress it again.
I'm having the same lock up issue on the Latitude 10 with MDT 2013. Did you ever figure this out?Sorry I haven't responded back to your question sooner.
But the answer is no. I stopped working on it for a while and just started to readdress it again. We have tried that. In fact, for imaging these we created a separate physical network so it doesnt effect our productivity environment.If we use inject drivers with a selection profile or the DriverGroup settings with ONLY the Latitude 10 drivers and windows 8.1 on MDT 2013 and Server 2012 (fresh installs - used for nothing else), it will image, reboot and stick at a black screen.If we image with no drivers - it reboots fine but doesnt end because it cannot connect back to network share.I have contacted Dell and they are having their CAB engineering team look into it. Unfortunately, we are in the US and they are in India so different hours. For now we are capturing an image and telling sysprep to persist the drivers in the image.
We have tried that. In fact, for imaging these we created a separate physical network so it doesnt effect our productivity environment.If we use inject drivers with a selection profile or the DriverGroup settings with ONLY the Latitude 10 drivers and windows 8.1 on MDT 2013 and Server 2012 (fresh installs - used for nothing else), it will image, reboot and stick at a black screen.If we image with no drivers - it reboots fine but doesnt end because it cannot connect back to network share.I have contacted Dell and they are having their CAB engineering team look into it. Unfortunately, we are in the US and they are in India so different hours. For now we are capturing an image and telling sysprep to persist the drivers in the image.Actually, I found the culprit. I don't know why I didn't think of disabling drivers. I thought it was something related to my config (either in the unattend.xml or in my task sequence) since there wasn't a driver issue with 8.
I too amusing Dell's driver cab. And I'm injecting the drivers with a DriverSelectionProfile. After a lot of re-imaging yesterday and today disabling and enabling different drivers along the way, I found the one that is causing the problem. It'sthe LNWIPC (INT33B5) driver.If you have not imported the drivers from the driver cab, move the 'IPC' folder (found in the 'chipset' folder) to somewhere else so that it doesn't get imported.If you have already imported all the drivers, find and delete 'Intel Corporation System LNWIPC.inf 6.2.9200.26576' from your Out-of-Box Drivers.If you have a mandatory application bundle like I have listed in a previous post, this driver will be installed with Intel Clovertrail UMA Graphic Driver. We have tried that. In fact, for imaging these we created a separate physical network so it doesnt effect our productivity environment.If we use inject drivers with a selection profile or the DriverGroup settings with ONLY the Latitude 10 drivers and windows 8.1 on MDT 2013 and Server 2012 (fresh installs - used for nothing else), it will image, reboot and stick at a black screen.If we image with no drivers - it reboots fine but doesnt end because it cannot connect back to network share.I have contacted Dell and they are having their CAB engineering team look into it. Unfortunately, we are in the US and they are in India so different hours.
For now we are capturing an image and telling sysprep to persist the drivers in the image.Actually, I found the culprit. I don't know why I didn't think of disabling drivers.
I thought it was something related to my config (either in the unattend.xml or in my task sequence) since there wasn't a driver issue with 8. I too amusing Dell's driver cab. And I'm injecting the drivers with a DriverSelectionProfile. After a lot of re-imaging yesterday and today disabling and enabling different drivers along the way, I found the one that is causing the problem.
Dell Latitude 10 Install Windows 8 1 Free
It'sthe LNWIPC (INT33B5) driver.If you have not imported the drivers from the driver cab, move the 'IPC' folder (found in the 'chipset' folder) to somewhere else so that it doesn't get imported.If you have already imported all the drivers, find and delete 'Intel Corporation System LNWIPC.inf 6.2.9200.26576' from your Out-of-Box Drivers.If you have a mandatory application bundle like I have listed in a previous post, this driver will be installed with Intel Clovertrail UMA Graphic Driver.Thanks for this!!!