Jump to content

[Solved] Win 8 and Shell_CharmWindow


Recommended Posts

Hi Everyone,

I hope someone is able to help me here, i want to detect the "Charm" windows in win8 in a hope to control them, but for now i can't even detect them as a window, does anyone know how i'd be able to detect the windows? specficly the window i want to detect is in win8 when you press "Winkey + I"

My initial idea was simple, but doesn't work (tho it might get the wrong Charm window still nothing)

WinWait("[Class:Shell_CharmWindow]")

msgbox(0,"yey", "yey")

So i went and tried with the name of the window, which in my case is "Indstillinger" Tho in english i'm guessing it's "Settings"

WinWait("Settings")

msgbox(0,"yey","yey")

This of course did not work either.

Ultimately what i want to do is to setup a Windows 8 none domain computer to a WPA2 Enterprise network with user credentials with out the user having to set this up manually. This we have done easily in windows XP, Vista and Win7 by using a "Wlan.exe" (Much like netsh, but for winxp as well) to import a wireless profile, this makes all the other windows pop up and promt for the user credentials, but windows 8 does not do this.

Update

-------------------------------

I've found a way to open the network window by sending a command, but still no way of detecting it.

rundll32.exe %SystemRoot%\system32\van.dll, RunVAN

Edited by CartoonDragon
Link to comment
Share on other sites

I took a look at this. There seems to be an additional layer of security built into Windows 8. You can see a similar behaviour with ProcessExplorer, whereas it can't see anything not spawned by the parent Explorer.exe process. Because the VAN screen can't be stickied, it is impossible to use Au3Info on it properly... which is a pain.

Anyways, I've never been a fan of using graphical automation of applications. You should look into other methods to connect to the wireless network, such as via the command prompt or PowerShell.

Using a .NET Class library:

http://managedwifi.codeplex.com/

Windows Native Wifi API:

http://msdn.microsoft.com/en-us/library/ms705969.aspx

Netsh in Windows 8:

http://thephuck.com/uncategorized/unable-to-edit-delete-wireless-profiles-or-networks-in-windows-8-use-netsh-wlan-to-fix/

http://techmell.com/windows-tips/create-connect-wifi-hotspot-windows-8/

Link to comment
Share on other sites

Because the VAN screen can't be stickied, it is impossible to use Au3Info on it properly... which is a pain.

I haven't looked at the VAN (?) screen, but you know you could unfreeze Au3Info, right? :huh:
Link to comment
Share on other sites

I haven't looked at the VAN (?) screen, but you know you could unfreeze Au3Info, right? :huh:

Yes, I can get the info from the the VAN (Network Connections) screen already, it is just different. Try it yourself and see what I mean... or maybe I'm not doing it right (this is totally a possibility) :D

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...