Windows 10: I just upgraded to Windows 10 home from Windows 7 home and now the Microsoft bluetooth...

I just upgraded to Windows 10 home from Windows 7 home and now the Microsoft bluetooth mouse's scroll wheel does not work. What can I do to get it to work? The other features work perfectly, just no scroll.

:)

 

Installing Windows 10 using Windows 7 key

Nope, you need to install Windows 10 first and make sure the Windows 7 key is transferred to your Windows account after you've installed Windows 10 (not quite sure how that works). I missed the last step and I could not activate Windows 10 after a re-install... Microsoft seem to have done everything they can to make it a PITA. Also, it's technically too late to do this now anyhow, as the upgrade offer has expired. But KMSPico works quite well...

As for getting rid of Windows, delete the Windows folder.

 

Installing Windows 10 using Windows 7 key

Nope, you need to install Windows 10 first and make sure the Windows 7 key is transferred to your Windows account after you've installed Windows 10 (not quite sure how that works). I missed the last step and I could not activate Windows 10 after a re-install... Microsoft seem to have done everything they can to make it a PITA. Also, it's technically too late to do this now anyhow, as the upgrade offer has expired. But KMSPico works quite well...

As for getting rid of Windows, delete the Windows folder.

 

Microsoft claims I signed up for Windows 10...

Click to expand... This is my list of hidden updates:

 

Microsoft claims I signed up for Windows 10...

Click to expand... This is my list of hidden updates:

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer