Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Windows 10 Upgrade ... Hardware Not Compatible  (Read 1912 times)

0 Members and 1 Guest are viewing this topic.

DaveLembke

    Topic Starter


    Sage
  • Thanked: 662
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Windows 10 Upgrade ... Hardware Not Compatible
« on: March 24, 2016, 09:40:17 AM »
Coworker today told me that his HP Desktop failed to take the Windows 10 free upgrade from 7 because the integrated GPU wasnt compatible. So he bought a cheap video card that is Windows 10 compatible and installed it. He goes to try to upgrade to Windows 10 since his system now meets the requirements and he is told he has to wait 30 days before he can upgrade. There is a 30 day hardware check lockout for Windows 10 upgrade.

I have never heard of such a thing, but I also have very limited exposure to Windows 10 upgrades. Anyone know anything about a lockout period in which you have to wait 30 days before you can upgrade to 10?

Allan

  • Moderator

  • Mastermind
  • Thanked: 1260
  • Experience: Guru
  • OS: Windows 10
Re: Windows 10 Upgrade ... Hardware Not Compatible
« Reply #1 on: March 24, 2016, 09:50:05 AM »
I have a hard time imagining that's true. This is certainly the first time I've heard of it, anyway. And a quick Google search doesn't result in any related hits.

DaveLembke

    Topic Starter


    Sage
  • Thanked: 662
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Re: Windows 10 Upgrade ... Hardware Not Compatible
« Reply #2 on: March 24, 2016, 10:09:31 AM »
I tried google too... figured I'd check here though.

BC_Programmer


    Mastermind
  • Typing is no substitute for thinking.
  • Thanked: 1140
    • Yes
    • Yes
    • BC-Programming.com
  • Certifications: List
  • Computer: Specs
  • Experience: Beginner
  • OS: Windows 11
Re: Windows 10 Upgrade ... Hardware Not Compatible
« Reply #3 on: March 24, 2016, 06:09:58 PM »
I found one comment on an article where somebody had this problem, it was related to how recently the version of Windows that was being upgraded had been activated, from what the commentor described.
I was trying to dereference Null Pointers before it was cool.