If occurring immediately and no response from ScreenBeam is shown on display:
- Turn Airplane Mode On and then Off.
- Try to connect to ScreenBeam receiver again.
- If still unable to connect, reboot the Windows device.
- If still unable to connect, remove ScreenBeam device profile as follows:
Windows 8.1
- Devices > Project > Add a wireless display
- Select ScreenBeam Receiver under Projectors heading.
- Click/Tap Remove Device; select Yes to confirm.
- Reconnect through Devices > Project > Add a wireless display.
Windows 10
- Open Device Manager
- View > Show Hidden Devices.
- Locate ScreenBeam receiver under “Miracast Display Devices” category.
- Right-click receiver > Uninstall
- REBOOT before attempting to connect to ScreenBeam again.
If the issue persists you will want to verify that the drivers on the PC are up to date, as the drivers used for the connection may be out of date and/or need to be reinstalled by visiting the PC manufacturers support site.
Comments
17 comments
I did everything as described, but it didn`t help
Klaus-Dieter, thank you for reaching out to Actiontec. Jim or I would like to assist with the issue you are experiencing. Please make sure to check your email for responses from Actiontec Support, including the "Spam" folder for replies. Once again, thank you.
Was this problem resolved? I am experiencing a similar issue. I have the latest drivers, latest BIOS, updated Windows 10 Pro and even checked compatibility using the latest Intel® WiDi Compatibility Tool. I always get the "Oops something went wrong" when trying to connect to my TV via the ScreenBeam Mini2 receiver (which has the 5.3.11.0 firmware). Can you please look into this? Thank you
My computer: NUC6i5SYH Operating System: Windows 10 Pro N 64-bit (10.0, Build 10586) (10586.th2_release_sec.160630-1736) Language: English (Regional Setting: English)
System Manufacturer: Intel
System Model: NUC6i5SYH
BIOS: SYSKLi35.86A.0045.2016.0527.1055 Processor: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (4 CPUs), ~1.8GHz
Miracast: Available, with HDCP
Graphics Card: Intel(R) Iris(TM) Graphics 540
Wifi Card: Intel(R) Dual Band Wireless-AC 8260
Mervyn,
Please check your email for responses from Actiontec Support, including the "Spam" folder for correspondence.
Thank you
Here we are, well into 2017. Device works fine with my Surface Pro 1, but refuses to work with my Surface Pro 4. I have tried the whole procedure but it flatly refuses to connect
Okay, after hours of trying I got a flash of inspiration. I had quite some Hyper-V virtual switches installed (that's what you get when you use Microsoft emulators, for Android or Windows Mobile) and apparently the ScreenBeam Mini2 gets VERY confused by that. Can this be fixed please?
Hello Joost,
This is not the ScreenBeam Mini 2 getting confused, as when the Hyper-V is in place the wireless connection is bridged and prevents Miracast, the standard protocol, from working correctly.
My laptop with win10 was connecting to my screenbeam mini2 just fine and all of sudden it doesnt want to connect to it before. Ive tried all troubleshooting methods listed. ALL OF THEM! please help. Like I said it was working just fine
Luis,
Please contact Actiontec by clicking the “Submit a request” button at the top right. An Actiontec technician will respond to your request as soon as possible.
Please note Actiontec support is available Monday-Friday from 8am-5pm MST
I am getting the same error; I have done all of the steps. Please help
I am getting the same error and these steps have not fixed my issue
Dennis,
Please contact Actiontec by clicking this link Open a Support Ticket or call 8884360657 to talk to a support representative.
My laptop with win10 was connecting to my screenbeam mini2 just fine and all of sudden it doesnt want to connect to it before. Ive tried all troubleshooting methods listed. ALL OF THEM! please help. Like I said it was working just fine
Lalit,
Usually, when this happens it is because your computer did an automatic update and one of your device drivers did not update. Have you checked to make sure all of your device drivers are up to date? If you have please give us a call.
Hi, My HP Omen laptop Windows 10 64 bit) tries to connect and I get the 'Oops, something went wrong' error 100% of the time but after a considerable amount of time of trying to connect. It doesn't happen immediately.
I can connect any of my Android devices to my Screenbeam mini 2 no problem.
This is needed for work so it's very important.
Firewall is off, Ant-virus is off and I've checked all the network settings etc.
Other older laptops have no difficulty connecting. What is going on?!
John,
The "Oops, Something went wrong" is usually caused by out dated graphics and wireless drivers on the HP Omen.
Since you state other devices (android phones & laptops) are able to connect without issue it verifies it is an issue with the HP Omen and not the ScreenBeam.
We do not recommend using the Mini 2 in a business environment. To learn more read this article.
Please sign in to leave a comment.