New
#21
As this machine is connected or has been connected to a domain, this may be the reason for the failure of the free upgrade, this offer, does not, and never has applied to commercial licences. The presence of AD or other entries on the machine could confuse the system to its origin and thus eligibility.
Well, I could dis-join it easily enough and re-join after the upgrade. I'm trying to remember though but it seems I did two other machines in the office without doing that. But my memory is shaky so I'll plan on the dis-join and try again.
It really bothers me that the error message I get from the exercise shows the following:
Still, I'll give it a try tomorrow after working hours.
Thanks...
This is from my rehabbed Dell Vostro 1510 that came with WinVista Upgraded to Win7 w/SP1 then to Win10:
Attachment 192689
Per: Windows 10 upgrades won't be free for everyone: Do you qualify? | ZDNet
Eligible for a free upgrade
- Windows 7 Service Pack 1 is required before you can upgrade using Windows Update. But all PCs sold with Windows 7, even pre-SP1, qualify for the upgrade.
- Windows 8 You must first upgrade to Windows 8.1 (free in the Windows Store) and then install the free Windows 8.1 Update from Windows Update. After that's complete, you're eligible for the free Windows 10 upgrade.
- Windows 8.1 You can upgrade to Windows 10 from Windows Update.
OK, I realize this article is 3 years old, but I think the author is correct. It makes a kind of sense to me. Microsoft was "hungry" for corporations to upgrade their client workstations to Windows 10 and I'd expect them to try to make it as "painless" as possible. Still, although I rather doubt it, you may be correct about no domains.
Certainly, they withdrew the GWX app after July of last year but one may still visit the windows 10 download site to obtain the Media Creation Tool. I've upgraded a number of PC's this way since January and I firmly believe that at least two were joined to my clients' domain when I did it (although I was using a LOCAL Admin account to do the deed).
If you have some MS authority to cite for the 'no domain members' idea, I'd like to see it.
Thanks for the info...
All I can find is this piece by Ed Bott back at pre release but He does not specifically rule out Domain computers but does state that Volume Licence based machines are excluded from the initial offer, but have other upgrade offers available. All I am stating is that the servers may be confused, by the presence of Domain or active directory markers, into believing these are not eligible although as a standard retail copy of pro they should be
Windows 10 upgrades won't be free for everyone: Do you qualify? | ZDNet
Yes, we're looking at the same article. I THINK the Volume Licensees had other avenues for upgrades but I'm not familiar with the T's & C's for VL customers. (I've never had one of those :) )
Anyway, I've added an EI.CFG file to try getting it to ask for the product key -- that way, I may learn if it's really a problem or if Win10 setup was merely confused.
Have a great evening...
This is really a puzzle but I'll take it.
Logged into PC still joined to domain as LOCAL Administrator.
I copied the ISO to the desktop from a flash drive.
I then added a file (EI.CFG) to the Sources folder in the copied ISO.
Contents of the file:I ran the setup file as Administrator and declined Updates.
[EditionID]
professional
[Channel]
Retail
[VL]
0
The thing ran to completion and started Windows 10.
I logged in as DOMAIN Administrator.
HOWEVER, when I checked, it had not activated Windows claiming product key trouble.
(I had not supplied a PID.TXT file in the Sources folder to go along with the EI.CFG file)
So, I clicked the Activate button and was told it couldn't activate with invalid product key.
So, I clicked on the TROUBLESHOOT button and voila, a few flashes and Windows was Activated.
It's now downloading and installing updates and looks to be a viable workstation.
When the updates are finished, I'll customize to mask the more objectionable crapware from MS.
SHOWKEYPLUS shows THREE product keys now; the two it showed previously, plus the default Windows 10 product key that results from a successful upgrade.
I honestly don't know why this seems to have worked, but I'll take it as a win!
I suspect (but cannot prove that) the EI.CFG file made SETUP defer product key checking until after installation and that the activation software in the complete Windows is a tad more robust than that in the setup.exe.
Does anyone have a better explanation for what went on here?
Thanks to all who've contributed...
Last edited by wyeknott; 19 Jun 2018 at 09:51.