Recommended Posts

You can skip the story and go to the bold part of the post for my problem.

 

So, i have a laptop that came preinstalled with Windows 8 (Homely). I would have probably upgraded to pro myself, but i still had 4 unused Windows 7 Pro keys so i put one of those on it and used it for 3 years like that. April-ish 2016 i upgraded to Windows 10 and apart from some inherited group policy settings from Windows 7 and some translation inconsistencies i haven't found big problems with it. It sat seldomly used by a family member for 3 months.

 

A couple of days ago i repossessed the machine and i noticed a bug that, after a boot the desktop icons would only show up after a right click, probably caused by some software that the person used at one time. I figured that it was not important and i would fix the problem when i got to it.

 

I went to repartition the machine using partitioning software and found that none of the 2 programs i used would do it. Note that i had the bios set to legacy mode before i installed windows 7 or upgraded to 10. I figured that it was due to some bootloader issue as it would skip calling out the partitioning program. I bet that it might have been caused by some bootloader/filesystem faults that were probably dued to cloning i did to the ssd i Windows on, because along the life of the device i had a 60 GB ssd on it, then a 240 GB and finally a 120 GB. Though i don't remember ever having problems repartitioning the disk inbetween any of those clonings on Windows 7, but that's neither here nor there.

 

So i went to install Windows 10 on that machine from scratch. It went quick and, i thought, painless. When i went to see if it was activated, because it was my first reinstall after the initial free upgrade i din in the spring, i found out i had the Home edition, but i was sure the machine had a Pro license. I quickly deduced it was because of the embedded BIOS OEM Key the machine had for Windows 8 (non Pro). I went to change the key (which i had saved beforehand) in the activation menu and it did not work. I found two solutions pretty fast. Either i had to reinstall 7 Pro and redo the upgrade, or i had to use an intermediary W10 default key and then use my own. Both worked with almost no issues, because i tested them. But for future reference, if i ever do it again on that machine (considering my average, probably not in the next 4 years) is there a way to force the Windows installation process to use my Pro Key?

 

I tried a suggestion from superuser.com to have a PID.txt file, but it did not read that. Maybe i formatted it wrong or it was a different file i needed to have. There used to be software, in the Vista/7 era that allowed one to edit the .WIM files from WIndows ISOs to remove or add versions from the media, to make it slimmer or add more options. I don't know of such software for Windows 10 and, so far, i haven't been able to force the setup to use the Pro Key and bypass the BIOS one. Can someone enlighten me on how to do that?

 

I have at least one other issue with Windows 10 inconsistency. Windows 10 has poor or incomplete translations for my language, when compared to 7. For example Program Files (x86) is translated to romanian (the language i chose on install) just fine, but the 64 bit one is just Program Files, in english. They were both translated fine in 7. There are a few others but you get the crux of it. That may be due to it being a lower tier language now compared to then, or it may be that all translations are not as good as they were, or that Windows 10 does not allow for folders such as Program Files to be translated (this last thing i honestly doubt). That's actually not the worst of it though. There are bigger translation transgressions if you upgrade from different languages of Windows 7 to Windows 10. So, when upgrading from Windows 7 romanian (as an example, because it's the one i use most) to Windows 10 (romanian) most (system) folders are translated to romanian, but if you upgrade from windows 7 english to windows 10 romanian there are even more folders not being translated, such Control Panel. And there is no way to fix it in post.

  On 08/08/2016 at 21:08, LauRoman said:

You can skip the story and go to the bold part of the post for my problem.

 

So, i have a laptop that came preinstalled with Windows 8 (Homely). I would have probably upgraded to pro myself, but i still had 4 unused Windows 7 Pro keys so i put one of those on it and used it for 3 years like that. April-ish 2016 i upgraded to Windows 10 and apart from some inherited group policy settings from Windows 7 and some translation inconsistencies i haven't found big problems with it. It sat seldomly used by a family member for 3 months.

 

A couple of days ago i repossessed the machine and i noticed a bug that, after a boot the desktop icons would only show up after a right click, probably caused by some software that the person used at one time. I figured that it was not important and i would fix the problem when i got to it.

 

I went to repartition the machine using partitioning software and found that none of the 2 programs i used would do it. Note that i had the bios set to legacy mode before i installed windows 7 or upgraded to 10. I figured that it was due to some bootloader issue as it would skip calling out the partitioning program. I bet that it might have been caused by some bootloader/filesystem faults that were probably dued to cloning i did to the ssd i Windows on, because along the life of the device i had a 60 GB ssd on it, then a 240 GB and finally a 120 GB. Though i don't remember ever having problems repartitioning the disk inbetween any of those clonings on Windows 7, but that's neither here nor there.

 

So i went to install Windows 10 on that machine from scratch. It went quick and, i thought, painless. When i went to see if it was activated, because it was my first reinstall after the initial free upgrade i din in the spring, i found out i had the Home edition, but i was sure the machine had a Pro license. I quickly deduced it was because of the embedded BIOS OEM Key the machine had for Windows 8 (non Pro). I went to change the key (which i had saved beforehand) in the activation menu and it did not work. I found two solutions pretty fast. Either i had to reinstall 7 Pro and redo the upgrade, or i had to use an intermediary W10 default key and then use my own. Both worked with almost no issues, because i tested them. But for future reference, if i ever do it again on that machine (considering my average, probably not in the next 4 years) is there a way to force the Windows installation process to use my Pro Key?

 

I tried a suggestion from superuser.com to have a PID.txt file, but it did not read that. Maybe i formatted it wrong or it was a different file i needed to have. There used to be software, in the Vista/7 era that allowed one to edit the .WIM files from WIndows ISOs to remove or add versions from the media, to make it slimmer or add more options. I don't know of such software for Windows 10 and, so far, i haven't been able to force the setup to use the Pro Key and bypass the BIOS one. Can someone enlighten me on how to do that?

 

I have at least one other issue with Windows 10 inconsistency. Windows 10 has poor or incomplete translations for my language, when compared to 7. For example Program Files (x86) is translated to romanian (the language i chose on install) just fine, but the 64 bit one is just Program Files, in english. They were both translated fine in 7. There are a few others but you get the crux of it. That may be due to it being a lower tier language now compared to then, or it may be that all translations are not as good as they were, or that Windows 10 does not allow for folders such as Program Files to be translated (this last thing i honestly doubt). That's actually not the worst of it though. There are bigger translation transgressions if you upgrade from different languages of Windows 7 to Windows 10. So, when upgrading from Windows 7 romanian (as an example, because it's the one i use most) to Windows 10 (romanian) most (system) folders are translated to romanian, but if you upgrade from windows 7 english to windows 10 romanian there are even more folders not being translated, such Control Panel. And there is no way to fix it in post.

Expand  

The translation problem could well be due to localization differences, and difference in tier since then is almost certainly a factor.  (It's not unique to Romania, either - certain languages in the Russian-localized versions of Windows 10 get the short end as well.)

  On 08/08/2016 at 21:21, PGHammer said:

The translation problem could well be due to localization differences, and difference in tier since then is almost certainly a factor.  (It's not unique to Romania, either - certain languages in the Russian-localized versions of Windows 10 get the short end as well.)

Expand  

That may be true, but it's kinda sad that things were better in 7 and Vista. What's even sadder is that, even though it had a kludgy way of doing it, and in all metrics it pales compared to Vista/7 (because it had no great translation backend) XP had better translations compared to 10, if you go by visible results.

 

Thanks for the answer, but my bigger issue than translation is being able to force the BIOS key bypass.

  On 08/08/2016 at 21:29, LauRoman said:

That may be true, but it's kinda sad that things were better in 7 and Vista. What's even sadder is that, even though it had a kludgy way of doing it, and in all metrics it pales compared to Vista/7 (because it had no great translation backend) XP had better translations compared to 10, if you go by visible results.

 

Thanks for the answer, but my bigger issue than translation is being able to force the BIOS key bypass.

Expand  

Well one had to pay for Windows 7 and Vista.

  On 08/08/2016 at 21:35, Gary7 said:

Well one had to pay for Windows 7 and Vista.

Expand  

Are you implying that if i buy Windows 10 starting July 30th 2016 i get a better translation on the disc or as any kind of download? You obviously aren't, so that's not an excuse, since the translation backend framework hasn't really changed since Vista.

  On 08/08/2016 at 21:48, LauRoman said:

Are you implying that if i buy Windows 10 starting July 30th 2016 i get a better translation on the disc or as any kind of download? You obviously aren't, so that's not an excuse, since the translation backend framework hasn't really changed since Vista.

Expand  

I am implying that if You did get it on or Before July 30, 2016 you could have done a clean install and activated your Windows 10 using a Windows outlook email address without a key.

  On 08/08/2016 at 21:08, LauRoman said:

But for future reference, if i ever do it again on that machine (considering my average, probably not in the next 4 years) is there a way to force the Windows installation process to use my Pro Key?

 

Expand  

You get to pick if you want Home or Pro during install. Or doesn't it let you pick which version you want to install?

Get installation media that *only* has pro, or extract the contents of your ISO to the drive, and use wintoolkit to remove the home image manually. My Linx 7 has a key embedded in the BIOS and using a pro only Windows 10 installation disc I was able to upgrade it to W10 pro rather than home.

  On 08/08/2016 at 21:55, Gary7 said:

I am implying that if You did get it on or Before July 30, 2016 you could have done a clean install and activated your Windows 10 using a Windows outlook email address without a key.

Expand  

Unfortunately, using the outlook email, has no impact on which version (Hoem or Pro) it gets activated to. If it read the bios oem key, which is 8 home, it activates to 10 home, regardless if i activated 10 pro after i upgraded from 7 pro.

 

  On 08/08/2016 at 21:58, FunkyMike said:

You get to pick if you want Home or Pro during install. Or doesn't it let you pick which version you want to install?

Expand  

No option shows up during install. Since i know of no way to force it to do pro (even if i had previously activated pro on it), it automagically reads the bios oem key for 8 home, and it activates to 10 home.

  On 08/08/2016 at 22:00, Gary7 said:

If you have a 7 pro the upgrade path is to 10 Pro.

Expand  

Your reply is, yet again, useless and completely misses the point of my issue, as were the previous two. I do not care about the upgrade path. I care about doing a clean install of 10 pro (a version i activated in april 2016) during the install of the os. SInce the bios of my laptop has a bios oem key for windows 8 home, the machine activates to 10 home. I have to do an activation dance to have 10 pro on it, since inserting my 10 pro key in the activation window of windows 10 home does not work.

 

It goes something like this:

 

option 1: Install windows 7 pro -> upgrade to windows 10 pro

option 2: Install windows 10 -> it activates to 10 home without my input -> serial key for 10 pro does not work -> using default serial key for windows 10 (VK7JG-NPHTM-C97JM-9MPGT-3V66T) -> it upgrades to pro -> use my 10 pro serial key -> it works

 

You do not seem to grasp that i want o jump over the those steps during install.

  On 08/08/2016 at 22:10, Javik said:

Get installation media that *only* has pro, or extract the contents of your ISO to the drive, and use wintoolkit to remove the home image manually. My Linx 7 has a key embedded in the BIOS and using a pro only Windows 10 installation disc I was able to upgrade it to W10 pro rather than home.

Expand  

I remember Win toolkit, and not wanting to use it because it was kludgy compared to other options available for windows 7 or xp, but i might give it a try. I hope that it works with WIndows 10 images.

  On 09/08/2016 at 02:17, LauRoman said:

Unfortunately, using the outlook email, has no impact on which version (Hoem or Pro) it gets activated to. If it read the bios oem key, which is 8 home, it activates to 10 home, regardless if i activated 10 pro after i upgraded from 7 pro.

 

Expand  

I understand that but at least it would activate, Windows 8 did not qualify only 8.1

  On 09/08/2016 at 02:17, LauRoman said:

No option shows up during install. Since i know of no way to force it to do pro (even if i had previously activated pro on it), it automagically reads the bios oem key for 8 home, and it activates to 10 home.

Your reply is, yet again, useless and completely misses the point of my issue, as were the previous two. I do not care about the upgrade path. I care about doing a clean install of 10 pro (a version i activated in april 2016) during the install of the os. SInce the bios of my laptop has a bios oem key for windows 8 home, the machine activates to 10 home. I have to do an activation dance to have 10 pro on it, since inserting my 10 pro key in the activation window of windows 10 home does not work.

 

Expand  

I would open the MS support app via Win 10 and ask them if they can deactivate Windows 10 home for your HWID/Account. Might be worth a shot.

  On 09/08/2016 at 02:17, LauRoman said:

I remember Win toolkit, and not wanting to use it because it was kludgy compared to other options available for windows 7 or xp, but i might give it a try. I hope that it works with WIndows 10 images.

Expand  

Removing the Home image should be relatively quick and simple. It does work with W10 images, I use it fairly frequently.

  On 08/08/2016 at 21:55, Gary7 said:

I am implying that if You did get it on or Before July 30, 2016 you could have done a clean install and activated your Windows 10 using a Windows outlook email address without a key.

Expand  

 

  On 08/08/2016 at 22:00, Gary7 said:

If you have a 7 pro the upgrade path is to 10 Pro.

Expand  

 

  On 09/08/2016 at 02:20, Gary7 said:

I understand that but at least it would activate, Windows 8 did not qualify only 8.1

Expand  

What are you going on about? I think i made it pretty clear in my first post that i want to activate 10 pro easier. The laptop in order, these operating systems

Windows 8 OEM -> Windows 7 PRO (Retail) -> Windows 10 PRO.

Because of the OEM key inside the BIOS (which is for 8 non pro). Windows 10 automactically activates to Home. IT DOESN'T MATTER THAT I HAD PRO ON THAT MACHINE, or that a specific 10 pro entitlement is tied to that machine or my microsoft account, IT STILL ACTIVATES TO HOME. If i want pro i have to do a whole activation dance or have to reinstall 7 pro and then uppgrade again. For future reference, and for other people that are now or in the future on the same boat, i would like to make the process shorter. and have it upgrade to Pro upon OS install since i have a friggin free license of 10 pro for that machine.

 

  On 09/08/2016 at 02:24, FunkyMike said:

I would open the MS support app via Win 10 and ask them if they can deactivate Windows 10 home for your HWID/Account. Might be worth a shot.

Expand  

Considering that there still are people that have successful activations, at this point it might just reactivate windows 10 home again. I might wait untill they disable free upgrades for accessibility users, to be safer.

  On 10/08/2016 at 14:56, LauRoman said:

 

Considering that there still are people that have successful activations, at this point it might just reactivate windows 10 home again. I might wait untill they disable free upgrades for accessibility users, to be safer.

Expand  

You could try to disable the SLP marker in the UEFI. Depending on which laptop you have there might be a tool that allows you to trigger the certificate information on and off.

 

This certainly exists for BIOS but the functional of switching it on and off might also exist for UEFI. I have only briefly touched upon this subject for UEFI laptops during my travels and I believe it is possible.

 

It is just a trigger in the SLIC table which turns this info on or off. There are OEM tools available for this.

 

Check MDL for such tools. You might have to search a bit.

 

I will try to enquire about it a bit and will let you know if I get some info.

 

What is your model?

So you have a few options:

 

Forcing the edition selection by putting a PID.TXT or ei.cfg into the installation. Very easy to do.

 

Disabling the SLP marker in the UEFI. If you have your model number then you can search MDL for such a tool but this is generally not advisable if you can cope with the first method.

 

Calling MS and removing the Home Edition when free upgrades end. (Don't hold your breath .. I have a feeling they are not bothered at all about people still activating it via old key / win 8 SLP markers.

 

 

  On 11/08/2016 at 18:53, r0wnin said:

You should have the option to delete the current key from your BIOS.

Expand  

Where?

This topic is now closed to further replies.
  • Posts

    • iPhone 17 Pro Max could have the biggest battery ever on an iPhone by Devesh Beri Leaks around how the iPhone 17 Pro lineup is going to look may have left fans hesitant about what Apple is planning for its next flagship, but not every rumor paints a gloomy picture. In fact, one area where the iPhone 17 Pro Max could truly stand out is its battery; rumors say it is to have the biggest battery ever seen in an iPhone. Let's be honest, battery life has long been a weak point for iPhones. No matter how efficient Apple's A-series chipsets are said to be, users often find their devices running out of juice quicker than expected. Much of the blame could be put on the relatively small battery sizes Apple has chosen over the years, especially when compared to the competition. Many rival brands now give their large-screen devices, those with displays bigger than 6.5 inches, batteries of at least 5000mAh. In contrast, Apple's largest iPhones have lagged behind in this department, with the iPhone 16 Pro Max coming in at 4676mAh. It seems like it is set to change with the iPhone 17 Pro Max, as a prominent leaker, Instant Digital, revealed that the battery of the iPhone 17 Pro Max will finally reach the 5000mAh mark. How big a change would it be? To put it in perspective, the iPhone 17 Pro Max's battery would be about 6.9% bigger than the iPhone 16 Pro Max, 13.1% more than the iPhone 15 Pro Max, and 15.7% more than the iPhone 14 Pro Max. If these rumors are accurate, the iPhone 17 Pro Max may finally address one of the most common complaints about Apple's flagship devices, but then again, Apple would still be lagging as most of the brands, specially the Chinese ones have already moved to the battery limits of 6000mAh and some have even touched 7000mAh. This rumor comes after the observation that Apple's struggles with AI may prompt it to transition Siri to either OpenAI or Anthropic's AI capabilities. Image source: Digit.in
    • Hope they laid off whatever middle managers thought it was a good idea to rebrand AAD as "Microsoft Entra ID" and Yammer as "Viva Engage," costing Microsoft some valuable brand recognition.
    • Microsoft removes PowerShell 2.0 from Windows 11 in build 27891 by Taras Buria Microsoft has released a new Windows 11 preview build from the Canary Channel. Build 27891 is out with several improvements and fixes, a new feature for the Microsoft Store, and the removal of PowerShell 2.0, which is now deprecated. Microsoft deprecated PowerShell 2.0 all the way back in Windows 10 version 1709. Last month, it issued a reminder about it, and now, PowerShell 2.0 is gone from the latest Windows 11 Canary builds. Microsoft says it will publish more information about PowerShell 2.0 removal in the upcoming update for Windows 11. Also, Microsoft is rolling out a new update for the Microsoft Store. Version 22406 is rolling out to Windows Insiders in the Canary and Dev Channels, offering the ability to install a product right from the Store's home page, as seen in the screenshot below: Here is what was fixed: [General] We fixed the issue causing the “Reset this PC” option under Settings > System > Recovery to not work after upgrading the last few Canary Channel builds. Fixed the underlying issue which was causing the taskbar to unexpectedly not showing acrylic material after upgrading to the latest Canary builds. This also impacted a few other scenarios, leading to unexpected black or white in some UI. Fixed an underlying issue believed to be the cause of some Insiders seeing Windows update downloads to get stuck at 2% recently. Fixed a few more languages including Vietnamese and Arabic that were still having issues with certain characters not rendering correctly for Insiders after the latest builds, causing nonsense to display in places like Task Manager and more. This impacted characters outside of A-Z. [File Explorer] Fixed an issue where if you opened the “…” menu in the File Explorer address bar to show the full list of folders for the current path, the dropdown might be cut off and the bottom of it inaccessible. [Settings] Fixed an issue in the previous build which could cause Settings to crash when opening microphone properties under Settings > System > Sound. Fixed an underlying issue related to Bluetooth which could cause Settings or Quick Settings to crash on launch for some people. [Windowing] Fixed an issue which was causing the window minimizing animation to not display correctly in the previous flight. [Task Manager] Fixed an issue where the CPU graphs in the Performance page were still using the old CPU utility calculations. Fixed an issue where after adding the new CPU Utility column, you might notice that System Idle Process always showed as 0. [Audio] Fixed an issue which could cause all system sounds to stop working (for example notification alert sound and the sound that plays when clicking the volume slider in quick settings), although audio in general was working on your PC. [Other] Fixed an underlying issue which was causing fonts in certain app menu items to unexpectedly appear corrupted or overlapped for some people. This also impacted typing in Word – where when using Hebrew a period may unexpectedly show as a 3, and in Thai typing space may show a 2. Fixed an underlying issue which could cause the playback controls in Media Player to become distorted in the latest Canary flights. Fixed an underlying issue believed to be the cause of LDAP queries from apps to take an unexpectedly long time in the previous flight. Fixed an issue which could cause print previews to appear slightly blurry in recent Canary flights. Here is the list of known issues: [General] [IMPORTANT NOTE FOR COPILOT+ PCs] If you are joining the Canary Channel on a new Copilot+ PC from the Dev Channel, Release Preview Channel or retail, you will lose Windows Hello pin and biometrics to sign into your PC with error 0xd0000225 and error message “Something went wrong, and your PIN isn’t available”. You should be able to re-create your PIN by clicking “Set up my PIN”. [Settings] [NEW] We’re investigating an issue in this build which could cause Settings to crash when interacting with the options under Settings > System > Power & Battery. [Remote Desktop] [NEW] You may see extreme graphical distortion and rendering issues using remote desktop on Arm64 PCs in this build. You can find full release notes for build 27891 in a post on the official Windows Blogs website.
    • Sounds like corporate spamming being painted as a "feature"...so long as it can be blocked like any other random creep messaging you, no biggie.
  • Recent Achievements

    • Week One Done
      Devesh Beri earned a badge
      Week One Done
    • Week One Done
      956400 earned a badge
      Week One Done
    • First Post
      loose_observer earned a badge
      First Post
    • Week One Done
      BeeJay_Balu earned a badge
      Week One Done
    • Week One Done
      filminutz earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      467
    2. 2
      ATLien_0
      159
    3. 3
      +FloatingFatMan
      150
    4. 4
      Nick H.
      66
    5. 5
      +thexfile
      62
  • Tell a friend

    Love Neowin? Tell a friend!