This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible

99

Solution 1

Do what the man said: Enable VT-X in the Bios.
Sometimes it is also called Hyper-V. (For some obscure reason it often is hidden in the "security" section of the Bios.)

Most computers ship with the setting disabled by default. Some computers (especially laptops) are technically capable of VT-x but the Bios doesn't show it so you can't enable it.
In that case you are sheer out of luck.

Solution 2

I get this error every time my Windows 7 Dell desktop restarts after a windows update. My CPU does support vitualization, and the BIOS is properly configured, but somehow the restart puts it in a weird mode.

Simple shut-down, and power on fixes the problem.

Solution 3

Go to BIOS by pressing ESC on powering on. Go to System Configuration -> Device Configuration or similar Check the enable VT-x Save Power cycle Should work

Share:
99

Related videos on Youtube

pixus nixus
Author by

pixus nixus

Updated on September 18, 2022

Comments

  • pixus nixus
    pixus nixus over 1 year

    I'm working on a class that generates a string made of random characters, of a given size. I'm passing the m_size value to the constructor, as you can see in the following code:

    class Random_Generator
    {
        using clock = std::chrono::high_resolution_clock;
        std::mt19937 m_dev;
        clock::time_point m_beginning;
        std::string m_value;
        size_t m_size;
    
        long long TimeSeed();
        std::string Generated();
    
    public:
        Random_Generator(size_t sz)
            : m_dev(TimeSeed())
            , m_beginning(clock::now())
            , m_size(sz)
            , m_value(Generated())
        {}
        // other methods
    };
    
    int main()
    {
        Random_Generator rstr(10);
        // more code
    }
    

    The thing is, m_size does not initialize with the value of sz: when debugging (I'm using Visual Studio community 2019, if that's useful), it seems that when the constructor executes, it simply jumps over the initialization of m_size, thus m_size having a garbage value.

    Any help would be appreciated!

    • Rob Moir
      Rob Moir almost 11 years
      So what is causing this error? - you've definitely checked the obvious idea that the error message means what it says and says what it means and that your BIOS settings need to be configured as described above?
    • Admin
      Admin almost 11 years
      thanks for the reply, but this is my first VM instaltion , so i would like to know if these is any supporting documentations of how i can solve this issue?
    • Rob Moir
      Rob Moir almost 11 years
      There's a decent enough explanation on the vmware knowledge-base article that you've included above as to what's going on and what to do. Beyond that, none of us can tell you what precisely how to do it for your laptop because this is going to be something that's specific to the BIOS in your computer rather than some standard we can rattle off for you that will work everywhere.
    • Jim B
      Jim B almost 11 years
      Here's a shot in the dark - perhaps enable VT...
  • Admin
    Admin almost 11 years
    thanks a lot for your reply, but i can not figure out how i can enable this on Intel core i7 on windows 7 64x on an HP laptop?
  • s_om
    s_om almost 11 years
    By reading the manual, or searching the fine Google
  • DavidPostill
    DavidPostill about 9 years
    This is not an answer to the original question. Please ask your own question (referencing this one for context if it helps). Lack of reputation does not stop you asking a question.
  • Khopa
    Khopa about 9 years
    A windows update did trigger the problem for me too, but shutting-down/powering-on did not fix the problem on an HP pro laptop. I had to re-enable virtualization in the BIOS, as it had been somehow disabled.