Share via

Intel Management Engine Interface

Anonymous
2009-07-21T01:47:27+00:00

Problem statement, M.E. yellow bang(!) in the device manager:

Intel Management Engine Interface

Device type: System devices

Manufacturer: Intel

Location: PCI bus 0, device 3, function 0

Running Windows Vista 32 Home Premium SP2.

All MS updates are currently installed.

Device status


"This device cannot find enough free resources that it can use. (Code 12)

If you want to use this device, you will need to disable one of the

other devices on this system.

Click 'Check for solutions' to send data about this device to

Microsoft and to see if there is a solution available."


I have updated the Intel DW965WH motherboard with the current

M.E. driver version 2.1.22.1033 .

No observable affect has occured.

Credible advice would be very welcome. Thanks.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2009-07-21T14:02:51+00:00

Hi dougbell,

Is this a recent problem? Was it working before?

If yes, you might want to do a System Restore to revert the changes back to the date it was work.

Running the<br>System Restore utility…
1.    <br>Click Start, click<br>All Programs, click<br>Accessories, click<br>System Tools, and then click<br>System Restore.<br><br><br>2.    <br>Click Continue or provide Administrator credentials if necessary.<br><br><br>3.    <br>Click Choose a different restore point, and then click<br>Next.<br><br><br>4.    <br>Select a Date and Time prior to first sign of the issue you’ve described.<br><br><br>5.    <br>If the date you need is in excess of (5) days click the<br>Show restore points older than 5 days check box.<br><br><br> <br><br><br>Important Notice:<br>That System Restore affects Windows system files, programs, and registry settings. It can also make changes to scripts, batch files, and other types of executable files on your computer. Thus, any recently<br> installed programs, updates, or changes to configuration will be lost if you use System Restore. However, make note that System Restore does not affect personal files, such as e-mail, documents, or photos, so it cannot help you restore a deleted file.

If not, then boot into Safe Mode and go to Device Manager, make a list of devices in the same category as the IMEI.  Reboot then do the same thing to see if there is any extra/ghost device that didn't show up in Safe Mode.  These device could be uninstall improperly and left behind by the system. 

Looking forward to hear from you soon,


Kevin

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forum and let us know what you think.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2009-07-22T02:15:08+00:00

    Hello Kevin, thank you for your reply:

    It was the "Windows 7 Upgrade Advisor" warning about M.E. requiring a compatible

    driver, which started this inquiry. Not knowing how long the M.E. warning

    existed, restore was not an option.

    In MS (online) docs about the "Code (12)" error message, it stated a

    device may actually be functioning properly.

    With a normal restart, the device list contained:

    UMBus Enumerator

    UMBus Root Bus Enumerator

    With Safe Mode restart, the device list contained only:

    UMBus Root Bus Enumerator

    Curiously, "UMBus Enumerator" location is: "on UMBus Root Bus Enumerator",

    while the "UMBus Root Bus Enumerator" location is: "Unknown"

    I disabled "UMBus Enumerator", restarted, M.E. still has the (code 12) condition.

    "UMBus Enumerator" is disabled (Code 22).

    "UMBus Root Bus Enumerator" is "...working properly".

    Both locations are the same as before the restart.

    A previous driver uninstall, restart, resulted with the "UMBus Enumerator" device having a driver.

    Again, there are no observable affects.

    So unless some resolution to this M.E. condition becomes available,

    I will eventually perform a Windows 7 clean install, rather than upgrade.

    The expectation would be to leave behind this and any other Vista "ghost" conditions.

    I rather suspect I'm not the only Vista user who would plan the same course of action.

    *End*

    Was this answer helpful?

    0 comments No comments