New Windows 10 Insider Preview Fast and Skip Ahead Build 17682 -May 31 Insider

Just noticed if type cmd into search although it appears can cannot run it at all! If I reboot it does run on the
reboot but only once. Very odd as the right clicking Powershell etc works fine. The mouse pointer changes from a pointer to an I, another words I cannot select anything from the dialogue box that appears.

Changed in Settings 'Replace Powershell with CMD on Right Click Prompt'..now works fine?!

Works here every time

smactilactus said:

Go to Settings/Ease of Access/Cursor and Pointer Size/Large Pointer Size and Inverted Pointer Color.

@Kari is not talking about the general Windows cursor but the cursor in a command/powershell session which is not related to the Windows cursor.

CountMike said:

Works here every time

Thanks..worked in all other builds. It's these little quirks that shows that what works on some setup's does not on others.

CallMeSteven said:

Thanks..worked in all other builds. It's these little quirks that shows that what works on some setup's does not on others.

Yeah, strange, somebody gets something and than other ones loose it. This i snot a lone example of that behavior.

cereberus said:

@Kari is not talking about the general Windows cursor but the cursor in a command/powershell session which is not related to the Windows cursor.

Exactly. My issue has nothing to do with pointer.

smactilactus said:

Strange happenings with a happy ending. So I tried typing cmd into search, and everything seemed fine. Then I did it again, and it broke both of my keyboards, the bluetooth and usb wireless. So I had to reinstall software for both. But that made me update my logitech software for my wireless usb mouse and keyboard, which has made my mouse ten times smoother than it was previously. I mean really noticeably better.
Here's the funny thing. Now that I have updated that software, I can type cmd into search, and it works fine on both the reg command prompt and admin prompt. Go figure...

I'm using Set Point 6.68.250 Latest version for my Logitech Mouse. Just reinstalled it and now the error has gone....puzzling

Kari said:

Exactly. My issue has nothing to do with pointer.

Have you tried the legacy console in properties?