how to remove intel graphics from context menu?

[sp_s]

im having HP 15 ab-031tx laptop with intel hd graphics and nvidia gforce 940. i updated to windows 10 and now the context menu is opening slow. i searched on line and found that removing the graphics processor option from the context menu helped. i was able to remove nvidia graphics option from the nvidia driver software, but coud not do the same for the intel hd graphics, kindly help in removing the option from context menu. thanks in advance.

[EstebanA_C_Intel · Accepted solution]

Hello, saranps:

I would recommend you to install all the Windows 10* updates and also make sure you are currently using the latest drivers for your different devices, chipset, graphics, etc.

If possible, you could also perform a clean installation of Windows 10* that could help.

This video could also help you with the issue; my recommendation before doing this would be to create a restore point for backup purposes.

https://www.youtube.com/watch?v=uNDhz3Hi65A How to fix windows 8.1 and 10 right click loading problem - YouTube

http://windows.microsoft.com/en-us/windows-10/create-a-system-restore-point Create a system restore point - Windows Help -

I look forward to your outcome with this.

Regards,

Esteban C

[sp_s]

Hello, EstebsnC_Intel

thank you for your responce.

my pc is always up to date and all the drivers are installed as per HP Support Assistant.

The video helped me a lot, i was able to remove the options from the context menu and the menu opened in a snap.

i already have my windows 8.1 backed up and have windows 10 and learnt how to bring back the options back, so no harm done:)

thanks for your help.

Saran

[EstebanA_C_Intel]

Hello, saranps:

Thank you for your answer.

I am glad to hear that you were able to fix the issue by removing this from the context menu.

If you require any further information or support, feel free to contact the Intel Communities again.

Regards,

Esteban C

[RDelt]

Have a look at

[EstebanA_C_Intel]

Hello, Delta-Roh:

Thank you for the additional route to other possible workarounds.

Regards,

Esteban C