Why do I immediately get the message “Oops, Something Went Wrong” or “Unable to Connect”?




  • Klaus-Dieter Sohn

    I did everything as described, but it didn`t help

  • Joe T.

    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.

  • Mervyn Naidoo

    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 firmware). Can you please look into this? Thank you

  • Mervyn Naidoo

    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

  • Joe T.

    Please check your email for responses from Actiontec Support, including the "Spam" folder for correspondence.
    Thank you

  • Joost van Schaik

    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

  • Joost van Schaik

    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?

  • Joe T.

    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

  • Joe T.

    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

  • Fabian Nelson

    I am getting the same error; I have done all of the steps. Please help

  • Dennis Scales

    I am getting the same error and these steps have not fixed my issue

  • Admin


    Please contact Actiontec by clicking this link Open a Support Ticket or call 8884360657 to talk to a support representative.

Please sign in to leave a comment.