virtualization technology stopped working

[starzennn]

I have a processor intel i7-3630qm, and as far as I know it supports technology vt-x, but recently it turned itself off and does not turn on in the BIOS, although it is on "enabled". checked by program LeoMoon.

[n_scott_pearson]

This forum is for the support of Intel NUC products. You obviously don't have an Intel NUC product.

All I can suggest is that you (a) ensure that you have the latest BIOS for your laptop installed (see your laptop vendor's site for updated BIOS releases - if they even maintain them any longer for 2012 laptops) and (b) use the following procedure to reset your the BIOS configuration:

1. Reboot laptop and enter BIOS Setup.
2. Load the configuration/optimal defaults.
3. Save settings and exit BIOS Setup.
4. Let system re-POST.
5. Enter BIOS Setup again.
6. Make any configuration changes necessary to enable VT.
7. Make any other configuration changes - but only those absolutely critical to allow your laptop to boot.
8. Save settings and exit BIOS Setup.
9. Test.

Hope this helps,

...S

[Jocelyn_Intel]

Hello, @starzennn  

Thank you for posting on the Intel® communities.  

We have a forum for this product and questions so we are moving it to the Processors Forum.  

Due to this product being discontinued, Intel Customer Service no longer supports inquiries for it, I am glad to see that fellow community members have the knowledge and they jumped in and helped. You may also find the Discontinued Products website, helping to address your request.    

You can get the specifications and verify this product's discontinuance status at the Intel® Product Specifications website > Marketing Status > "Discontinued":  Intel® Core™ i7-3630QM Processor   

Please keep in mind that this thread will no longer be monitored by Intel. Thank you for your understanding. 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[Bill-091374]

I had a similar issue initially and it may not be the same as your issue. Once I updated the BIOS with microcode updates Docker stopped working with Windows WSL. Somehow WSL support was disabled in Docker. I simply re-enabled WSL support in Docker and things went back to normal for me. I hope this helps.