9/4/2019 FAQ: Windows 8.

1 and Windows 10 AdHoc network support solution – Global Caché Support Portal

My activities Submit a request Sign in

Search 🔍

Global Caché Support Portal > General > Tech Tips & Solutions

FAQ: Windows 8.1 And Windows 10 AdHoc Network Follow

Support Solution
RELATED ARTICLES

Starting with Windows 8.1, Microsoft reduced support for Adhoc Wifi networks.  Previous iTach FAQ's
As a result, Windows 8.1 does not detect or display Adhoc networks in the list of Windows 8.1 Pro and ad hoc WiFi
networks
available wireless networks (also known as the "wireless network picker").  
FAQ: My Flex Wifi unit is not connecting
Windows 10 behavior is slightly different, as it does detect and display available to the wireless network

Adhoc networks, but when attempting to connect, it fails with a "Cannot Connect How do I get iHelp to discover my unit?
iHelp Download
to Network" error.

This is a problem when using Windows 8.1 or Windows 10 to perform initial

setup/provisioning of iTach WiFi or iTach Flex WiFi devices.

Some WiFi adapter manufacturers provide their own wireless management

software with support for Adhoc networks.  However, if this is not the case, a

workaround procedure is described below to allow manual connection to Adhoc

networks, using the Windows command shell.

Also any iOS device (iPhone, iPad, iPod), or Mac OS X device can connect to ad-

hoc networks and can be used to perform the configuration of the Global Caché

device.

UPDATE - 8/24/2016 - We have created a script called AdhocConnect.exe to

automate this process. It is considered to be a beta release, so may not work

in every scenario. It is attached at the bottom of this FAQ. Please try it out

and send any feedback to support@globalcache.com

The following gif shows an example usage of the AdhocConnect.exe script.

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 1/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal

After the connection is completed by the AdhocConnect.exe script open a

browser and continue setup per normal setup instructions by entering the unit's

default IP address in your browser.

Note: If the AdhocConnect.exe script gives an error including "ibss type not valid"

this may mean that the wireless card in your machine does not support Adhoc.  In

these cases a different device must be used.

Manual Entry

If you would like to manually enter the commands the instructions are maintained

below.

Because the wireless network picker in Windows 8.1 does not show Adhoc

networks, connection must be done with several manual steps. 

(A text file is attached containing all required commands and instructions,

allowing cut/paste of commands, and a find/replace of the <ssid>

parameter).

From the Start Menu, find and launch "Command Prompt", or type

"cmd.exe" and <ENTER> in the search box.

To see all networks in range, including Adhoc, run the following command

in the command window:

> netsh wlan show networks

SETUP

The following must be done once for each network:

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 2/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal

Go to "Network and Sharing Center"

Click "Set up a new connection or network"

Double click "Manually connect to a wireless network"

Enter the SSID of the adhoc network (as shown by "netsh wlan

show networks") into the "Network name" field

Configure security settings accordingly

Uncheck "Start this connection automatically" (important)

Click "Next", then "Close"

Run the following command. Replace <ssid> with the SSID of your network

for all following commands:

> netsh wlan set profileparameter <ssid> connectiontype=ibss

***NOTE***

For Windows 10, the command is:

> netsh wlan set profileparameter <ssid> connectiontype=ibss

connectionmode=manual

CONNECT

After setting up, run the following command whenever you want to connect:

> netsh wlan connect <ssid>

Replace <ssid> with the SSID of your wireless network.

Hovering over the WiFi icon in the system tray will show the name of the

network you are currently connected to, even if it's an adhoc network (the

network picker will not show it if it's adhoc). The name is also visible in

"Network and Sharing Center" window.

DISCONNECT

To disconnect from the adhoc network connect to a different network, turn

off WiFi, or run the following command:

> netsh wlan disconnect

CLEANUP

To remove the network profile from Windows, run the following command:

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 3/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal

> netsh wlan delete profile <ssid>

Source: http://answers.microsoft.com/en-us/windows/forum/windows8_1-

networking/windows-81-ad-hoc-not-showing/5d75d887-ff59-425e-a480-

9f80ada63627

An additional note on Adhoc. There have been reported issues with the need to

enable Adhoc mode within the Wireless Adapter drivers for the PC.

Go to Device Manager-->Network Adapters--><your wireless adapter>--

>Advanced.

There may be a setting for Adhoc mode available. If attempting to connect to

Adhoc with an iTach that uses 802.11b, do not have 802.11n Adhoc mode

enabled.  Please let us know other examples that you find within the driver

settings by commenting on this post.

***Microsoft Surface devices do not support Adhoc in the embedded wireless

chipset in use.**

There is also another utility available that does not require the command line

solution that is outlined above.

Download the Wi-Fi Scanner found here: http://lizardsystems.com/wi-fi-scanner/.

After running, the iTach or Flex may show up in the list of broadcasting devices.

Right-click on it and select "Connect". If it is successful, try opening a browser

and entering the default IP of the iTach (169.254.1.70) or Flex (192.168.1.70). If

the device has connected, the web configuration page will appear, and you can

proceed with configuring the device to connect to the local SSID.

It may be necessary to Disconnect the device with the Wi-Fi Scanner after

completing the configuration.

 
Windows10_Adhoc.txt (856 Bytes)
AdhocConnect.exe (1 MB)
AdHocConnect.gif (300 KB)

Was this article helpful? 👍 👎 5 out of 5 found this helpful

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 4/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal
Have more questions? Submit a request

19 Comments Date Votes

 Brian Kerth October 09, 2015 07:54

0
Added command modification to instructions necessary for

Windows 10.

⚙Comment actions ▾

 Brian Kerth November 04, 2015 08:42

0
Added additional suggestions for configuring the Wireless Adapter

settings

Added link to Lizard Systems Wi-fi Scanner utility.

⚙Comment actions ▾

 Steve Miller December 01, 2015 11:27

0
Tried adding a WF2IR manually per above and connecting via

Lizard Systems.  Neither works.  The only way I can connect to this
module is with a Win7 PC.  What else can I try?

⚙Comment actions ▾

 Brian Kerth December 17, 2015 00:38

0
Steve,

There may be an additional configuration on the Network Adapter
Card that allows you to "Enable Adhoc" or something similar. If
this doesn't work, contact support@globalcache.com and we can
troubleshoot further.

⚙Comment actions ▾

 Jignesh Vaghela May 19, 2016 21:34

1
I tried but unable to proceed because i am getting an error "The

BSS type is not valid"

It neither works with windows 7. it follow all the procedure and

connected but Led above Power cord continuously on, NOT
BLINKING.

Kindly help for this.

Thank you  

⚙Comment actions ▾

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 5/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal

 Quint Jackson May 22, 2016 03:20

0
Using Windows 10 - Failed again after entering "netsh wlan set

profileparameter GlobalCache000C1E039D72 connectiontype=ibss
connectionmode=manual" got message "Failed to modify the
profile. Error 0x8000D: The BSS type is not valid."

⚙Comment actions ▾

 Quint Jackson May 22, 2016 05:30

0
Using Windows 10 on another computer and the procedure

described above worked - both computers using same version of
Windows - the difference is network adapter for when it didn't
work is Intel dual band Wireless AC7265.  Adapter that did work is
"<no name> 802.11 Wireless LAN card"

⚙Comment actions ▾

 Brian Kerth August 24, 2016 23:56

0
If you have a Microsoft Surface Pro, Adhoc is not supported in the

Marvell Wireless chipset. You will not be able to use a Surface Pro
to connect via Adhoc.

⚙Comment actions ▾

 Manfred Ottenbreit September 04, 2016 02:34

0
I'm very happy to found this ... Struggled wit gaining access to a

TP-LINK w-lan printserver ...

I tried lot of different things with "netsh wlan" settings but coud
not make it under windows10.

Due to your precise and detailed explanation it works.

FYI: during my several trial and errors I have also set the Qualcom
Atheros AR9485 profile > AdHoc 11n = Enable

Thank you!

⚙Comment actions ▾

 Shekhar Kumar September 13, 2016 23:44

0
This method worked for me smoothly, Though I failed to connect

when I had WEP security ON on my Nokia E5 (the ad hock WiFi hot-
spot). With open WiFi it worked perfectly. I want to say thank you
very much. I am running on Win 10 64 bit. All in all it's working.

⚙Comment actions ▾

 mhtest eddie December 23, 2016 20:00

0
You can easily create a wireless adhoc network in Windows 8 and

10 using this simple application -

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 6/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal
> http://www.easyaslinux.com/tutorials/wireless-ad-hoc-network-
windows-8-10/

⚙Comment actions ▾

 Vegard Kolbeinsen June 20, 2017 18:25

0
I keep getting "unable to connect to this network" I tried running

the AdhocConnection.exe but still not able to connect to the unit.

Tried resetting too, is the unit malfunctioning?

⚙Comment actions ▾

 Scot Marc June 21, 2017 02:44

0
We followed ALL examples given here.  We also turned on the

AdHoc feature in the wifi hardware driver.  No errors displayed. 
The iTech device still does not display in the Edge or Internet
Explorer Browser.  This machine is Windows 10 Creator Update. 
Please advise.

⚙Comment actions ▾

 armin July 15, 2017 12:35

0
Windows10. iTach's SSID shows in wifi list but gives "can't connect

to this network" error. tried all suggestion above. still get the
same error. please help

⚙Comment actions ▾

 armin July 24, 2017 07:22

0
I went back and used an older computer (still windows 10) which

had a wifi board with its own software. Connected at the first try.

⚙Comment actions ▾

 Ingenieria Preventa July 25, 2017 06:41

0
I have a problem with my itach flex WiFi tried to connect to the

network it emits but it says "I can not connect to the network" I
have windows 10 and I followed the steps that the support portal
says and it does not work for me.
How do I configure it and access the network it broadcasts?

⚙Comment actions ▾

 Tony Renstrom December 27, 2017 21:35

0
Same problem and manage to find a fairly simple solution that

works.

1. Use an Ipad and connect directly to the Itach here.

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 7/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal
2. Make sure to go to info on the network and set your IP to static
in the same range as the Itach

3. For some reason the default browser will not work (safari) The
only browser I got to work is Chrome

This worked following a very long trial and error. Once I finally got
my computer to connect to the network it would not display
anything in the browser.. Once i got the ipad to connect the safari
browser would not display anything.. Once i managed to connect
on the ipad with the iCab browser it would not save the settings..
only thing that worked was the above instructions.. Hope this is
helpful (if you have an ipad.. prob. works with iphone as well)

⚙Comment actions ▾

 Erik Maher December 13, 2018 15:15

0
I spent several hours struggling with this until I realized that your

commands don't match what Windows 10 (or at least my version
of Windows 10) is looking for.  Shouldn't your command netsh
wlan connect <ssid> instead be (where ssid is optional unless
there is more than one ssid in the profile):

netsh wlan connect <profilename> <ssid> ?

Shouldn't your command netsh wlan delete profile <ssid> instead

be (without ssid at all):

netsh wlan delete profile <profilename> ?

Shouldn't your command netsh wlan set profileparameter <ssid>

connectiontype=ibss connectionmode=manual instead be:

netsh wlan set profileparameter <profilename> <ssid>

connectiontype=ibss connectionmode=manual ?

When I was typing them in your way, nothing was working.  Then
when I typed them in the way Windows 10's built-in help indicated,
the commands worked smoothly.  That being said, the delete
profile command was unnecessary as setting and starting the
hostednetwork never created a profile (so there was nothing to
delete), and the set profileparameter command was unnecessary
as the adhoc network was already working after connecting to the
hostednetwork from the other laptop.  I seem to have had an
entirely different experience than what you and some of the other
readers posted but my adhoc wifi network is now working
beautifully so I'll shrug my shoulders and move on.

⚙Comment actions ▾

 Sonya Finkey March 15, 2019 07:37

0
Thank you!!!

...for your beautiful little program AdhocConnect.exe.  It works
perfectly in our Windows 10 Pro version 1809.  At long last, we
got into our Delta-T Pro Lite WiFi controller by Heliodyne that
delivers solar heated water to our water heater. We are truly
grateful!

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 8/9
9/4/2019 FAQ: Windows 8.1 and Windows 10 AdHoc network support solution – Global Caché Support Portal
⚙Comment actions ▾

Please sign in to leave a comment.

Powered by Zendesk

https://globalcache.zendesk.com/hc/en-us/articles/114094165352-FAQ-Windows-8-1-and-Windows-10-AdHoc-network-support-solution 9/9