Operation is blocked, waiting for opblock", or,

"Not accepting messages at this time" (or something of sort, don't remember it word for word), here is how you solve it:

You need to make sure your SSID you have inputted is not the same as any of the already existing Ad-hoc networks you may have stored.

The program will create a new virtual adapter device on your computer, named Wireless Adapter 2.

For it to all work properly, first you have to make sure your drivers actually do support this virtual operations. To do that, click Start, type "cmd", right-click "cmd.exe" and select "Run as Administrator". Once there, type:

netsh wlan show drivers

Scroll up a bit and find the line saying "Hosted network supported: " and if it says "Yes", you're good to go. If it says "No", please download the latest drivers for your wireless adapter.

If you manage to start the wireless network and your device shows "Limited connectivity", you need to Share the internet connection (through LAN or DSL or whatever) to the WiFi network yourself. To do that, open Network and Sharing Center, click the "Local Area Connection", click "Properties", and select tab: "Sharing".

Make sure you check all the boxes, including "Allow devices to use this internet connection", and select "Wireless Adapter 2" as the network to share *to*, from your LAN.

IF at this point you get the error message saying that the process/device "is not accepting status messages at this time", you need to do the following:

Click Start, type "cmd", and right click "cmd.exe" and select "Run as Administrator". Type:

netsh winsock reset

You will get a message saying that Winsock catalog has been reset and you need to restart your computer. Do it now, and after the OS is up, you should now, with little bit of luck, be finally able to start the wireless network using Virtual Manager, connect to it with your device and be able to access internet.

IF NOT (of course!), you need to check your IP settings.

IP settings:

Go to Network and Sharing Center, click "Wireless Network Connection 2", and click Details,

Then on your device (while you're connected to the WiFi network), simply tap the network name in Wireless settings pane. Check the TCP/IPv4 settings on computer and IP settings on your device.

The first three network segments must match, the 4th segment must be "1" on your computer, and anything else on your device. For example:

On computer:

192.168.1.1

On device:

192.168.1.15

If your IP settings on your device are wrong, tap and hold the WiFi network for a second, and select Modify Network, under IP address select "Static" instead of "DHCP", and input your correct settings.

Next, the Subnet Mask should always be 255.255.255.0

All the rest should be left blank on your computer.

On your device:

Gateway is the IP address of your computer, in our example "192.168.1.1". Gateway is, to put it bluntly, the first node your device bumps into when going to internet.

Copy the "DNS" server from the "DNS server" field on your PC on your source Connection. Meaning, if you have internet over LAN, Click Local Area Connection (in your Sharing Center), and copy it's DNS Server into corresponding field on your device. Bluntly put, DNS server is the boss of the network, it determinates to which device does which data packets go, and how. DNS supplies teh internetz to your PC, to your device and all devices in your own subnet branch (your house or maybe neighborhood, depending your network ogranization). So this boss is same for all devices.

Make sure you get the password right Dizzy Face

Congratz, you can now access the internet on your Android.

Now, if you still do not have internet access on your smartphone, then you're definitely