Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hvandrie

Profile Information

  • OS
    Windows 7 x64
  1. Jaclaz, Thanks! Actually, there's no 3rd command. And, just checked the requirement for the 3rd inf file netvwifimp.inf, but I can't find any dependencies. I did include it because it was referred to in another fora that described how to add wireless support for WinPE 3.0. So, I think you may ignore it, at this moment. What I did to test some things is to export profiles on a working windows system using netsh wlan export profile command, and import profiles in WinPE using the netsh wlan import command. Be sure to first start the wlansvc service prior to starting netsh in WinPE. Also, the easiest way to add the registry part for the LEGACY_WLAN keys and values, is to add registry permissions for <computername>\Administrators on the Enum and/or Root subkey in the registry keypath once you've loaded the System hive into your registry editor. I am gona work on an automated way to achieve this required part, well... wanna automate the whole stuff when I have some time. In order to connect to a enterprise wireless network that uses PEAP and MSCHAPv2 for user authentication, you need to use either some coding in .NET or use AutoItv3. I found the latter to be most easiest way to achieve this goal, will test a compiled piece of code that some guys already shared here: http://www.autoitscript.com/forum/topic/91018-native-wifi-functions/page-4 Cheers, Herman v3
  2. MacShuffle, I've got the missing piece of your puzzle. Thanks to your extended information, and the info I too found for WinPE 3.0, I now have it working correctly on WinPE 4.0 and 5.0. First, you do not need to implement "WcmSvc", or "Windows Connection Manager", service. When you create the wlansvc service and it's listed in the "DependsOnService" entry of the server, just remove the entry wcmsvc from the reg_multi_sz key. Second, the error wlansvc cannot start with error "The handle is invalid (error 6) is because you're missing a file in your configuration. You need an additional schema file copied into your WinPE 4.0/5.0 image: "WLAN_profile_v2.xsd". Source location in your full blown Windows is: "C:\Windows\L2Schemas\WLAN_profile_v2.xsd" . Third, certain wireless adapter drivers have an "Include" in their .inf file to include an additional virtual adapter driver, like Intel have. When you open such a driver file, search for "Include=". In all latest Intel Wireless drivers, you'll see listed: "Include=netvwifibus.inf" To add this to your WinPE 4.0/5.0 image, copy the following files to the following locations in your WinPE image: Windows ---> WinPE image C:\Windows\Inf\netvwifibus.inf ---> <mountdir>\Windows\Inf\netvwifibus.inf C:\Windows\System32\Drivers\vwifibus.sys ---> <mountdir>\Windows\System32\Drivers\vwifibus.sys And, very important: C:\Windows\System32\Drivers\vwifibus.sys --> <mountdir>\Windows\Inf\vwifibus.sys Somehow, it only works properly when the .sys file is (also) included in the <WinPE>\Windows\Inf folder. Fourth, the drvload command to load netnwifi.inf, netvwififlt.inf and netvwifimp.inf won't work. You get the signature error, and copying the catalog files won't help. Though, I did now copy them as well, here's how to load the services from the 3 net*.inf files once WinPE 4.0/5.0 is booted: netcfg -l %SystemRoot%\Inf\netnwifi.inf -c s -i MS_NativeWifiP netcfg -l %SystemRoot%\Inf\netvwififlt.inf -c s -i ms_vwifi And, voila... you now are able to start the wlansvc without a problem and use netshell command (netsh) to see and add wireless network profiles to connect to. Oh, little detail: sometimes the wireless driver doesn't load fully, most likely due to the two stage install of the virtual adapter driver. I used devcon rescan to let WinPE do a redetection and than it automatically started working properly. Have fun!!! Herman v3
  • Create New...