forsberg94

Thanks guys! Adding the KDMF driver solved the problem! Appreciate the help here.

Thanks for the responses, Tried *not* injecting the driver via DISM and then booting into a vanilla WinPE and using the drvload.exe command. No Luck. I'm not able to find old drivers for this device from the Lenovo site. Having trouble navigating the Intel Download Center. I am looking for the MEI driver (formerly HECI). Thanks again guys! HWIDs of the Intel® Management Engine Interface: PCI\VEN_8086&DEV_9C3A&SUBSYS_221417AA&REV_04 PCI\VEN_8086&DEV_9C3A&SUBSYS_221417AA PCI\VEN_8086&DEV_9C3A&CC_078000 PCI\VEN_8086&DEV_9C3A&CC_0780

Having an issue with a driver working in WinPE 4 (Version 6.2.9200), but not WinPE 3 (6.1.7600). I am attempting to install an Intel vPro MEI (Management Engine Interface/HECI) driver into WinPE. I am using a Lenovo X240. Using a vanila WinPE image in both instances (both 32 bit). Injecting the driver (which is for Win 8.1, 8, & 7) with Dism. Using the driver from the Lenovo Driver Site (Intel Management Engine 9.5 Software for Windows 8.1 (64-bit), 8 (64-bit), 7 (32-bit, 64-bit) || 26 Jan 2014 || Version: 9.5.22.1760) - extracted package and using HECI.inf in the drivers folder. - Lenovo X240 MEI driver works in WinPE 4.0 (Microsoft Windows [Version 6.2.9200]) o PE Image built with Windows AIK - Lenovo X240 MEI driver does NOT work in WinPE 3.0 (Microsoft Windows [Version 6.1.7600]) o PE Image built with Windows ADK Version numbers taken from the command prompt command in WinPE: ver How can I move forward in getting the driver working on Version 6.1.7600? Thanks for any help!

Hi all, Having an issue where WinPE hostname is not being resolved properly. Here is my issue: Assumptions: Hostname in Win7 = win7hostname (Private IP: 172.16.50.100) Hostname in Win PE = winpehostname (Private IP: 172.16.50.100) Win PE's firewall is taken down using the following command: wpeutil disablefirewall - When I am in Windows 7, a DNS record is created on the DNS Server. When I look at the DNS Server (Win Server 2008 R2 x64), I see a record in the DNS Manager for win7hostname I can do ping 172.16.50.100 and receive a response I can do ping -a 172.16.50.100 and receive a response which resolves the address to win7hostname I can do ping win7hostname and receive a response (which it resolves to 172.16.50.100) - When i am in Win PE (firewall down), a DNS record is not being created on the DNS Server. I can do ping 172.16.50.100 and receive a response I can do ping -a 172.16.50.100 and receive a response which resolves the address to winpehostname I cannot do ping winpehostname and receive a response. Fails to resolve to any IP address. I am confused because I do not see a DNS record when I am in Win PE, but when I try ping -a 172.16.50.100 I see the correct hostname in the command prompt (from the DNS Server). I cannot, however, resolve that hostname when I attempt to ping it. Any suggestions or comments would be greatly appreciated! Thanks!

It seems this is a feature of the netsh wlan command. You can only import a salted password XML file into the same computer that it was exported from. Even though this is the same computer, since it is using a different OS (Win PE), it is thinking that it is not. The only workaround that I can provide for this is the following: netsh wlan export profile name="Test_AP" key=clear this will result in the command generating an XML file with a clear-text password of the Wireless AP's security key. Importing the profile with the clear-text XML file will work on any other computer.

I am having another issue with the netsh wlan utility Netsh not connecting to secured AP Any help on this post would be much appreciated Thanks guys!

Hey everyone. I was able to get the command line tool: netsh wlan working in Win PE 3.0 thanks to JFX's help in the following thread http://www.msfn.org/board/topic/152480-netsh-wlan-issues/ I am having a strange issue now though. If I export a secured Access Point's profile in my instance of Windows 7 x64 Professional, It will not connect via the command line in Win PE (as shown in the following image) WinPE netsh wlan screenshot This Access Point has WPA2-Personal enabled. If I change this Access Point to have no security, then the Win PE netsh wlan command can add and connect to this profile with no problem. Also, If i export the above profile (with WPA2-Personal), using the following command: netsh wlan export profile ASsU_2.4 key=clear , Win PE can import this xml profile just fine and connect to it without any problems via the command line. This last command will export the profile to an XML file with a clear text password. So WinPE netsh wlan is having trouble decrypting the passwords to use to connect to the AP. Also, there is only one SSID associated with this profile, so adding that parameter to the connect command does nothing. Does anyone have any thoughts as to why this could be the case?? Any help is much appreciated!! Thanks - Chris

[sOLVED] That worked like a charm!! Thank you so much. Been pulling my hair out thinking that it was another .dll file that i was missing. I appreciate your help! [sOLVED]

Hi all, I am having an issue with the netsh.exe utility in WinPE 3.0 that I was hoping you could shed some light on. So by default, when I type netsh wlan it cannot find the 'wlan' switch. I added the following .dll files and added an entry to the registry to utilize that dll in: HKEY_LOCAL_MACHINE\Software\Microsoft\NetSh "dhcpclient"="dhcpcmonitor.dll" "wshelper"="wshelper.dll" "4"="rasmontr.dll" "2"="ifmon.dll" "netiohlp"="netiohlp.dll" "wlan"="wlancfg.dll" Above is what I now have in that NetSh folder in the registry. Now when I type netsh wlan the command is found, but I am getting an error which I have never seen before. The error I am seeing is as follows: Error 15105 in FormatMessageW() The linked image is a screenshot of just typing 'netsh wlan', and then below in the screen is where I type 'netsh wlan show profiles' http://i.imgur.com/uItdv.jpg I hope you can help me out. Thanks in advance!