Now that the upgrade program has officially ended, what changed and what remains the same? Seems like the GWX and the standard upgrade assistant no longer work. The "Assistive Technologies" upgrader works (for now). What about running Setup from the DVD?
Yesterday the normal upgrade still worked to get a HWID, have exhausted all my testsystems, only vmwares
I just did a test machine that was never on Windows 10, and after typing in it's Windows 7 key, it... activated normally. 8) Seems the upgrade ending was followed by a huge "*WINK WINK*"
The AT upgrader is the only thing that allows me to do "free" upgrades now. GWX I understand is no longer offered through WU, and I believe it may be removed soon for those that have it?
Does w7 + DAZ loader + online validation as a base for the genuineticket.xml still get w10 activated on a device that has never had w10 installed before? Or do I have to go through the hassle of using the assistive technologies updater that will download the installation files and go through the painful update procedure from now on? Thanks.
Did this route (Win 7 Ultimate + Daz loader => Win 10 Pro) work for you on Vmware yesterday you mean? From USB media I might add, and all the way to validated...
Something tells me that an awful lot of people with disabilities using ATs will suddenly appear out of nowhere to claim their free W10 upgrade. Let's hope they don't also claim welfare benefits, or our taxes will double.
News to me, but I just read where Microsoft has change the hardware specs to make 2GB RAM for 32 bit systems the minimum required. Mostly that won't affect me but I do have a couple of netbooks with 2GB RAM running Windows 10 x86 very well. It'll be interesting to see how the Anniversary update works with them. This may be the thing that pushes me back to Linux Mint for them. No matter, I like Linux Mint and I have images. My son has a laptop with 3GB RAM on his x64 Windows 10 installation. That one worries me a bit, but he likes Windows 7 so we'll see.
Unless I'm mistaken that's a requirement only for new 32-bit OEM systems sold with 1607 pre-installed.
I can just confirm that this still works fine, you can even use an old Win 7 media without servicepack 1. I wonder, as Vmware is "all virtual", wouldn't the fingerprint/HWID created be identical, (Or very similar) on a lot of machines? Hence maybe you can fresh install without going thru the Win 7 hoop, as it will be registered on MS servers already the first time somebody did the upgrade?
One big thing that happened, I use MSN.COM for my home page.....No more FREE Windows 10 ads.....it's about freaking time !!!
Hey, good news. Today I gave the known good method of w7+Daz+online validation and genuineticket.xml a try on an old Core Duo Sony notebook and a custom cheap PC. Used w10 Pro v1511 as the fresh w10 install for the xml file... both activated successfully. So, it "ended" on the 29th... or probably this has to do with the assistive technologies upgrade that's still in place allowing activation to happen.
Well, the Start menu look changed yet again, I wonder when MS will settle down to something final. I also wonder how those that installed the Classic Shell start are affected.
Now that's interesting. So if I install a 32 bit retail version of 7 on a machine with 1GB RAM, and upgrade it to Windows 10, I can install the anniversary update. I'll have to check that out. On a somewhat different note, I installed the Anniversary Update on three x64 machines last night and this morning. For the most part it went really well. I installed via the downloaded Upgrade Assistant. I’ve had no compatibility issues and so far all machines have been running quite well. Many of my privacy settings were reset during each installation so they had to be put to where I wanted them. The only real “problem” I have is that Alphawaves’ Windows 10 Login Changer no longer is able to bypass the lock screen. When I tried to use it, I got an error message saying changes would have to be made via Settings. On my virtual machine, the process started well with the system check saying my disk space was sufficient. But when I started the actual update, it failed saying there was insufficient disk space. No matter, that’s a project for a different time.[FONT="][/FONT]
Yes, can't say I like it. 1511's was better IMO. However it's old news for Insiders and those of us following updates on tech sites. I believe Classic Shell has already been updated for RS1, so don't see what the problem is. Users should be fine as long as they update and their settings should remain intact.