Start a Conversation

Unsolved

This post is more than 5 years old

C

93314

February 1st, 2016 07:00

Optiplex 3010 Win 7 32bit - fix required for win10 incompatibilty

Folks,

My optiplex 3010 with win 7 64 bit is fully compatible with windows 10 and I can upgrade it to win 10 if I want to.

But win 7 32 bit, installed on the same machine but on a  separate partition to win 7 64 bit, and activated, is not compatible with windows 10 according to the MS upgrade tool. I know the i3-2100 processor can run win 10 and I've installed the MS KB compatibility fix and enabled DEP etc. Does anyone else have this problem or know of a fix for this machine that will enable me to upgrade the win 7 32 bit to win 10? Thanks 

9 Legend

 • 

87.5K Posts

February 1st, 2016 09:00

32-bit Windows 7 can only be upgraded to 32-bit WIndows 10 -- in fact, you cannot upgrade any 32-bit Winodws install to 64-bit -- the OS needs to be installed clean in order to install the 64-bit version.

1 Rookie

 • 

47 Posts

February 1st, 2016 11:00

I thought my question was clear, but maybe not. This is about upgrading from win7 32 bit to win 10 32 bit. Its got nothing to do with upgrading from win 7 32bit to win 10 64 bit, and nothing to do with upgrading from win 7 64 bit to win 10 64 bit.

On my optiplex 3010 running win 7 32 bit, the ms win 10 upgrade tool says my CPU is incompatible with win 10. I know the i3-2100 CPU is compatible with win 10 32 bit so besides the ms KB fix and the DEP fix  what might the problem be please?

9 Legend

 • 

87.5K Posts

February 1st, 2016 12:00

Check your BIOS setup - is the NX bit (execute disable) disabled?  There is a setting on at least some OptiPlex systems to enable/disable -- that must be enabled for Windows 10 to install.

1 Rookie

 • 

47 Posts

February 1st, 2016 14:00

Its the latest BIOS A15 and the bit is enabled. (Checked)

9 Legend

 • 

87.5K Posts

February 1st, 2016 15:00

1 Rookie

 • 

47 Posts

February 2nd, 2016 04:00

The upgrade option is working now, without me doing anything else. Waiting a few days after making the config changes was the solution, even though I'd reset and run schtasks.exe.

No Events found!

Top