WiFi connection working but with limited functions - No network scan possible

My Win10XPE runs successfully in general.
The WiFi-network connection itself works.
I can surf with the browser in Internet.

However sometimes I would like to help friends with the setup of their network.
In order to investigate their Wireless network I normally start a network scan to detect their devices in local WLAN.

Therefore I use well known (free) network scanner like
- WifiInfoView https://www.nirsoft.net/utils/wifi_information_view.html
or
- HomeDale https://www.the-sz.com/products/homedale/

Unfortunately these tools are not able to find any other device in LAN/WLAN "as usual".

Why?

No cash occurs. Just the list of found other computers remains empty
ipconfig /all
shows a valid adapter

Since the network connection is setup not by the normal built-in Win10 function but by the additional "PE network" tool
I guess that the network functions provided by PE Network are somehow limited.

Any idea on how to solve this problem?



Toby

Hi Toby,

i just ran a test on "my" current PE version and the good news is, both programs are working fine. Bad news is, I dont know why you are seeing issues :)

I attached 2 Screenshots of my PE Base config. You might want to give that a try.

@PetePossum:

Very interesting.

I setup every options exactly as you did....but it still does not work.

I traced with "Process Monitor" what WifiInfoView did at last and found that it searches for a file

X:\Windows\SysWOW64\Wlanapi.dll

and didn't found it (see attached snapshot)

Its in the install.wim of the source ISO (Win2004).

But it seems that it is NOT copied (by PEBakery v0.9.7b7 from 28 Aug 2020) to target folder + ISO.

Similarly another program tried to access

X:\Windows\SysWOW64\rasman.dll

and didn't find it either.

Why?

I suspect PEbakery does not copy all stuff from source ISO to target.

Could you check if your booted Win10XPE contains these files?

Thank you
Toby

Hi,

I can confirm that I have both files in my X:\Windows\System32 folder. Also the corresponding version in the syswow64 folder.

I am building with WinBuilder 082, using 1909 as source.

I am still on 1909 because I am using a printer addon, which I was not able to get working on 2004. I was also facing some bluescreens on some maches using 2004 as source.

it would appear the WifiInfoView is 32 bit program and requires the SysWoW64 system files to support the program.. You must include the required system files in your process.

Here is an update...

I checked the base files and did not find any information about the 2 files in question. However, I have a plugin called DOT11Expert, which is similar to the 2 programs you were talking about. It adds wlanapi.dll if not already present.

you can fnd it here:
http://theoven.org/index.php?topic=2607.msg33348#msg33348

Not sure about RASMAN.DLL yet...

PS: Dot11expert is not running anymore, complains about license. However, it added the file ;)

I added the two files via

\Projects\Win10XPE\Features\WoW64_AddFiles.txt

It works now (for the critical plugins).

Very strange that these base files are not added automatically.

I wonder how many files will I possibly miss in future (for other plugins)....

Very strange that these base files are not added automatically.

Well I guess ChrisR could have just copied 'all files' but it's balanced against speed and size
and what is necessary for the project as it's distributed, to work fully.

When you create your program applications - you need to use [AddFiles] or [AddFiles6432] to extract the required system files from the install.wim used by your application

I put now another 2 files

\Windows\SysWOW64\en-GB\KERNELBASE.dll.mui
\Windows\SysWOW64\en-US\KERNELBASE.dll.mui

into

\Projects\Win10XPE\Features\WoW64_AddFiles.txt

But they are NOT added in the final build.

Why?

Hi

as Jimehc suggests, you would normally use the [AddFiles] or/and [AddFiles6432]  on a per XPEPlugin basis 

eg

Code: [Select]

ExtractSectionFiles,%ScriptFile%,AddFiles
If,%Architecture%,Equal,x64,ExtractSectionFiles,%ScriptFile%,AddFiles6432

[AddFiles]
\Windows\System32\??-??\propsys.dll.mui
\windows\System32\propsys.dll
\Windows\SystemResources\propsys.dll.mun

[AddFiles6432]
\Windows\SysWOW64\??-??\propsys.dll.mui
\windows\SysWOW64\propsys.dll

nb.  this obviously assumes that the resource exists in the particular source ISO you're using