My mouse cursor is invisible on the boot menu gui - HELP!

Its invisible when on the graphical metro boot menu... It only recently got like this.. How can I fix?

This glitch(?) is annoying me..

Anybody have any ideas of how to restore the visible mouse arrow on the gui boot menu?

I have the same problem and have raised another thread for it. However, you can navigate the panel using the Tab key or the arrow keys.

BobD said:

I have the same problem and have raised another thread for it. However, you can navigate the panel using the Tab key or the arrow keys.

Yea I've been using the arrow keys..

Hope somebody knows of a fix..

I now know why but it is a Microsoft fix.

I have a machine with multiple Win 10 Pro partitions. Two of these have been upgrades where I started the install from a mounted ISO and let Win 10 install. Tonight I did a clean install (booted off a USB key) of Win 10. While that clean install is the default boot then the GUI boot menu shows a mouse pointer. As soon as I make one of the other systems the default then I lose the mouse pointer.

I'm not about to clean install my other two partitions so its off to Microsoft to report a problem.

BobD said:

I now know why but it is a Microsoft fix.

I have a machine with multiple Win 10 Pro partitions. Two of these have been upgrades where I started the install from a mounted ISO and let Win 10 install. Tonight I did a clean install (booted off a USB key) of Win 10. While that clean install is the default boot then the GUI boot menu shows a mouse pointer. As soon as I make one of the other systems the default then I lose the mouse pointer.

I'm not about to clean install my other two partitions so its off to Microsoft to report a problem.

Well seems you have narrowed it down...

I have win7 PRO installed and win10 PRO installed (which was first an upgrade from win8 PRO and then a clean re-install from the USB install media)

Hope your report to MS gets acknowledged, thanks!

Larry
I posted the problem on the Microsoft forum. I have one response so far. Check it out for yourself.
Bob

I found another reference to this problem here . It was in the blog at the end of the article. The other guy, Francois, knew about the problem and it happened only when upgraded. I was also a contributor to that blog under the name of Fred.

BobD said:

I found another reference to this problem here . It was in the blog at the end of the article. The other guy, Francois, knew about the problem and it happened only when upgraded. I was also a contributor to that blog under the name of Fred.

Thanks, still waiting for a fix from MS