MDT failed with DRIVER IROL NOT LESS OR EQUAL

Eaven HUANG 2,126 Reputation points
2024-03-06T00:45:42.36+00:00

Dear All,

I'm using MDT to deploy OS for some LENOVO models like ThinkBook 14 and we faced an issue - after the image was applied and the computer rebooted, it showed "getting started 9%" then out of sudden it went into the blue screen saying DRIVER IROL NOT LESS OR EQUAL. I googled around and was advised to create a pure boot image and injected the proper drivers for the specific model.

Is it the case? If yes, how can I create a new boot image in MDT without touching the original one we have (we used total control for the default image).

Thank you very much.

DRIVER IROL NOT LESS OR EQUAL

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,749 questions
Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
830 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 40,321 Reputation points Microsoft Vendor
    2024-03-06T03:05:23.8166667+00:00

    Hi, @Eaven HUANG

    Thank you for posting in Microsoft Q&A forum.

    It seems the issue is not with your WinPE boot image, it is the driver of the deployed OS.

    That issue is an incorrect or missing driver for something in the deployed OS.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

  2. Wesley Li 4,815 Reputation points
    2024-03-13T09:36:02.7866667+00:00

    Hello

    Was all the process automatic? Did the error occur after you chooose the deployed image (applying image part) or in the PE process(task option part)?

    Usually this error should be related the driver you configure with the deployed driver if the eror occured after the applying image process.

    If the error occurred after we boot into MDT task immediately, then the issue could be related to the PE part.

    Anyway, we could try to check whether there is any dump file (memory.dmp file) created in C:\Windows (if the issue occurred in applying image part) in PE command mode(press shift +F8 in MDT UI or just boot the machine from a PE).

    If therere is no disk partition created, then the issue could be related to the boot image, we could concentrate on the boot image part. Create a new deployment share could be an option if you don't want to affect present MDT configuration. Please remember to replace the boot image in WDS boot image option.

    0 comments