All i get is a black screen with one faint red bar down the left side. It shows the Windows logo, and the loading circle, just will not go into MDT. Anyone else seen of have this issue? What ADK are you using? ADK You mention P53s, but I want to clarify. I have not seen an issue with either the P53 or the P53s. It is version This is runnin on Windows serverand as far as I can tell ,the latest version I can be running.
I am using P53s, the model, but i am trying to do 5 of them. Kind of confusing. I am going to try and update everything, as i noticed that it can run the latest, and test. It can be found here.
If you check Programs and Features on the server and look for the Windows Assessment and Deployment Kit installation and the version associated is I strongly suggest getting on ADK or newer preferably for the latest hardware compatibility.
Most older hardware should be compatible with these builds. Thanks, updating everything got me into the MDT items, but now all I am getting is a command prompt. One issue down, one more to go hopefully. Maybe same issue. When trying to image any P53s model laptop the image fails to load right after the windows load screen, and a small blue line appears on the left of the screen.
From that point on, the screen stays black. I have tried injecting drivers into the boot image. Still no progress.After using a new captured image Win 7 x64 certain machines were not completing OSD and ending up at a black screen with just a mouse cursor.
Dell T, E, E, M This was after the May patching, the only update that has been reported to play up well with flash? We removed this patch from the base and the problem no longer occured. It's possible that it affects machines with the nic ILM, but probably a revision as it did not happen on the Update: I think it is to do with driver injection and i7 cpu's.
We still had some issues after this with drivers not installing correctly on i7's. Using the x64 boot wim resolved this. I also had this issue since the beginning of this year. It seemed to mainly affect newer Dell models, such as the ones you mention and the Optiplex But I can confirm that using the x64 boot image does indeed work.
I would like to know the cause of the problem, but at least for now we have something that works! Hi, thanks for your comment. Don't know why but I think it's something to do with the dism. Someone's MS ticket being logged helped us! Do you have any update about this. We have the same situation with the black screen using the boot image x We know that using the boot image x64 fix this but we prefer to continue to use x86 for the moment. Hey, no update unfortunately. We have fully moved to the x64 wim which required some apps to be converted to x I would experiment using different versions of Dism and it's required files in your situation - Check the links in the windows 10 post for what those files are but do similiar with x86 files.
I was experiencing this issue on a Lenovo M91 and Ts laptop. I haven't tested the laptop yet but I assume it will work. The intel drivers I had in my SCCM database was fromI updated it with the latest one and from intel which was and all is good now.
Your email address will not be published. Home Latest Posts About. June 15, by Jay Connor. Trevor September 9, Reply. HS September 10, Reply. Roberto October 7, Reply. HS October 7, Reply. Iggy Pi January 20, Reply. Leave a Comment Cancel reply Your email address will not be published.Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Learn More. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services.
You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number. I have a WinPE 3. It gets past the "Starting Windows" screen and the screen just goes black, but I can see and move the cursor. I thought maybe it was a driver issue, but it works on other machines with the same hardware.
Thank you for visiting Microsoft Community and providing us with the detailed description about the issue. As I have understood, you are experiencing issue with black screen on the system.
I certainly understand your concern and will try my best to help you. I really appreciate all your efforts in trying to fix this issue. I would suggest you to refer to the article given below and check if that helps. Why is my screen black when I start windows 7. Note: This section, method, or task contains steps that tell you how to modify the registry.
However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.
How to back up and restore the registry in Windows. Please do let us know if you need any further assistance, we will be glad to assist you.
Did this solve your problem? Yes No. Sorry this didn't help. I'm not sure why that response was marked as the answer, since it did not actually solve the problem. I tried everything listed in your response along with many, many other things I found with no success.
I eventually just wiped the hard drives. Once the hard drives were wiped, I could boot into WinPE again. So, I re-partitioned and imaged again. The mystery is, therefore, unsolved. However, based on my experience during this process, my theory is that for some reason Windows Boot Manager?
As you have not responded to the thread but steps provided by Jayant was relevant to the issue which you have posted. That is the reason why his steps were marked as answer. So that if other community members face the same issue can try the steps provided by him.A message appears: "No bootable image found, notebook will shutdown".
Although I learned through experimentation that 1GB works without any problems. My solution: I've created a package including my bootx We are seeing the same issue.
I tried to copy the files but the S drive doesn't exist. Is it a partition? Nothing special.
This partion will host the OS-Bootloader files later. Didn't find what you were looking for? Ask the community or Ask the Virtual Agent. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for.
Did you mean:. It has been a while since anyone has replied. Simply ask a new question if you would like to start the discussion again. All forum topics Previous Topic Next Topic. Level 1. Message 1 of 7. HP Recommended. Product: Elitebook G2.
Operating System: Microsoft Windows 10 bit. All looks good. It seems there are different SecureBoot checks implemented in different laptop models. Thanks a lot in advance.
WinPE boots to black screen with crusor
I have the same question. Tags 6. Tags: AdminCR. New member. Message 2 of 7. Did you ever get this problem solved? We encounter the same symptoms with G1 - G3. Message 3 of 7.Incorrect function. An action failed. Execution of task sequence failed.
Once I know I had a clean HD to begin with if an error or problem still occurs then I go looking in to the logs. Usually from a command windows "F8" I will map to the network drive of my 'tech pc' and copy the log files to there so that I can use a better editor than notepad on the target. Well you could spend some time, and therefore money, in trying to do intensive scans on the hard drive and possibly get the bad sectors list on the HD updated and hopefully all the bad sectors will be found and properly marked as bad If nothing else find a different HD temporarily.
I can apply a Norton Ghost image fine to the machine, it's only when applying the MDT build that the issue occurs. The article below indicates it may be a problem with the diskpart which would make sense. I think Norton Ghost uses sector based imaging, please let me know if I'm wrong. Assuming that some sectors went bad during normal use of the computer the OS would have ensured that when writing data to the HD that it did not write to a bad sector.Import Dell WinPE Drivers into MDT Litetouch
Not an IT pro?
Subscribe to RSS
Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Solution Accelerators. Microsoft Deployment Toolkit. Sign in to vote. Wednesday, May 26, AM. Hi EN, the first thing I do when a deployment fails is to boot to the DS and when it asks for credentials I press "F8" to open up a command window and "clean" the hard drive removing and trace of a failed deployment, this also causes a loss of ALL DATA on the hard drive.Keep in touch and stay productive with Teams and Officeeven when you're working remotely.
Learn More. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services.
You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
I've had Windows 10 64bit installed for a while without issue; however, upon my most recent boot, I'm getting a black screen with no mouse immediately after the Windows 10 logo and spinning dots. The computer doesn't progress past this point. I have tried rebooting 3 times to get into system recover mode but a similar situation occurs - I get the Windows logo with spinning dots with "Starting System Recovery" along the bottom, followed immediately by a black screen.
I have a monitor hooked up via. DVI and a TV hooked up via. HDMI to the onboard ports- both are displaying the same screen content. I am at wits end and I have spent way too much time failing. Reaching out to the community for help.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I suggest you to disconnect all the external devices printers, scanner, USB universal serial bus drives, etc Except mouse and the keyboard and then boot up. Try to perform Automatic Repair in Windows recovery tool that can fix certain system problems that might prevent Windows from starting.
Automatic Repair scans your computer for the problem and then tries to fix it so your computer can start correctly. Press any key. Did this solve your problem? Yes No. Sorry this didn't help. April 7, Keep in touch and stay productive with Teams and Officeeven when you're working remotely.
Site Feedback. Tell us about your experience with our site. Mubir Created on January 7, Hey, I've had Windows 10 64bit installed for a while without issue; however, upon my most recent boot, I'm getting a black screen with no mouse immediately after the Windows 10 logo and spinning dots. After doing some research online, i've done the following: I have tried rebooting 3 times to get into system recover mode but a similar situation occurs - I get the Windows logo with spinning dots with "Starting System Recovery" along the bottom, followed immediately by a black screen.
I have the same question User Replied on January 7, To download the Windows 10 ISO refer the link below.Forum Rules. Help Register Login. Latest Threads. Results 1 to 8 of 8.
Windows 10 - no boot - black screen after logo
I used to be able to boot MDT not booting to x86 Lite Touch. I used to be able to boot to x86 Lite Touch on a client and then select the Install OS task sequence.
However now when I boot into the x86 Lite Touch image all I get is the 'Vista like' progress bar on a black screen and does not boot into the logon screen, etc. I can boot into the x64 Lite Touch image but there are no task sequences set up x64 OS's.
But now all of a sudden it won't? When I boot into x86 it just hangs at the 'Vista' progress bar. Any help is appreciated!
Have you added any new drivers lately? Then refreshed the boot images to import into WDS. OK, in your boot images driver selection only tick network drivers and regenerate. I'm pretty sure I checked that yesterday but will try again next time in the school.
Thanks for the reply! I have all network and all mass storage enabled for my boot images. I once found with my x64 image that after I had added a load of additional drivers and reenerated the images it didn't boot. How do you just specify certain types of driver files? Right click on the deployment share, properties, windows pe x86 components. Tags for this Thread mdtwdsx64x The time now is PM.
All rights reserved. Copyright EduGeek. Follow EduGeek via.