Nice move to invalidate older keys, indeed :D

Not invalidate them so much, but sneakier, tie it towards your PC hardware signature. I forgot this key quote earlier:

New problems and complicated activation issues are now rising as your license key is tied towards your unique PC hardware signature.

Which may mean that when you add or change a GPU, you need to buy a new license.
When you add RAM, new license.
When you add an audio card, new license.

Now with the added supplement of not being able to go back to Windows 7/8.1 without needing to buy a new license for these as well.

And perhaps that MS is busy with a fix for all this, but it doesn't look like they're trying to get one out too quickly.

---

Nice move to invalidate older keys, indeed :D

Not invalidate them so much, but sneakier, tie it towards your PC hardware signature. I forgot this key quote earlier:

New problems and complicated activation issues are now rising as your license key is tied towards your unique PC hardware signature.

Which may mean that when you add or change a GPU, you need to buy a new license.
When you add RAM, new license.
When you add an audio card, new license.

Now with the added supplement of not being able to go back to Windows 7/8.1 without needing to buy a new license for these as well.

And perhaps that MS is busy with a fix for all this, but it doesn't look like they're trying to get one out too quickly.

Exactely this happened to my win 8.1 partition.
I upgraded it to win 10 and you might remember my GPU died 3 weeks ago.
Now i can`t activate win 10 anymore.

---

With each crime and every kindness we birth our future.

Just released Today, Ubuntu 15.10 (Wily Werewolf)
http://releases.ubuntu.com/wily/
My copy is downloading now. When it finishes I'll make a bootable USB drive and give it a spin.

Nice move to invalidate older keys, indeed :D

Not invalidate them so much, but sneakier, tie it towards your PC hardware signature. I forgot this key quote earlier:

New problems and complicated activation issues are now rising as your license key is tied towards your unique PC hardware signature.

Which may mean that when you add or change a GPU, you need to buy a new license.
When you add RAM, new license.
When you add an audio card, new license.

Now with the added supplement of not being able to go back to Windows 7/8.1 without needing to buy a new license for these as well.

And perhaps that MS is busy with a fix for all this, but it doesn't look like they're trying to get one out too quickly.

Considering that it was possible to re-activate Win7 after similar hardware change I would call it key invalidation still. Staying with prior Windows version one could keep key active but spending that key on Win10 he will lose it much faster and be forced to buy new one. That's key invalidation.

I have an optional KB3095649 update waiting for me that is a bit weird. For when you follow its link - https://support.microsoft.com/en-us/kb/3095649 - to the Knowledge Base, you'll find it's an update for Windows 8.1 and Windows Server 2012 R2 only.

I have Windows 7 SP1.

So either it's an update also for Windows 7, or it isn't and you're looking at a blue screen of horror at the reboot. I will not install it.

---

I have an optional KB3095649 update waiting for me that is a bit weird. For when you follow its link - https://support.microsoft.com/en-us/kb/3095649 - to the Knowledge Base, you'll find it's an update for Windows 8.1 and Windows Server 2012 R2 only.

I have Windows 7 SP1.

So either it's an update also for Windows 7, or it isn't and you're looking at a blue screen of horror at the reboot. I will not install it.

Did a Google search and found this forum thread about it.

http://www.sevenforums.com/windows-updates-activation/383962-kb3095649-another-mystery-meat-update.html#post3164517

It looks....safe, but still weird that it is documented as an 8.1 update and does not mention that it is for 7 at all anywhere. But it is also supposed to be an unchecked optional update in 7, supposedly. Most people are choosing to just hide it until MS decides to be at least a little bit more clear about either A) what specifically it does, or B) why win7 systems are getting an 8.1 update.

I find both A and B quite unlikely to ever happen, with A being far more unlikely than B.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

wusa /uninstall /kb:3065987 /quiet /norestart
wusa /uninstall /kb:3083710 /quiet /norestart
wusa /uninstall /kb:3083711 /quiet /norestart

You're missing KB3065988 in this one.
But then you may not want to uninstall them immediately, as these updates add the group policy addition through which you can instruct your Windows not to upgrade to Windows 10.

True, KB3065987 and -88 install the diagnostic tracker, part of the telemetry. But this one can on its own be deleted, doing from a commandline:

sc stop Diagtrack
sc delete Diagtrack

But it now shows that even with all the updates removed, stuff is still lingering on many systems. Like these:
From the Task Scheduler Library->Microsoft->Windows, remove
Everything under "Application Experience"
Everything under "Autochk"
Everything under "Customer Experience Improvement Program"
Under "Disk Diagnostic" only the "Microsoft-Windows-DiskDiagnosticDataCollector"
Under "Maintenance" "WinSAT"
"Media Center" and click the "status" column, then select all non-disabled entries and disable them.

And, under services.msc:
Set "Remote Registry" to "Disabled" instead of "Manual".

---

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Installing Linux Mint is very easy indeed, but beware a hardware upgrade.
Installing new graphic drivers is a pain in the a**.

yes it is .. graphic drivers are an issue .. I've not been able to work my way through that portion as yet

i may be speaking to soon and still have some tweeks to do .. but one Linux box up and running .. working on graphic driver

---

Installing Linux Mint is very easy indeed, but beware a hardware upgrade.
Installing new graphic drivers is a pain in the a**.

yes it is .. graphic drivers are an issue .. I've not been able to work my way through that portion as yet

i may be speaking to soon and still have some tweeks to do .. but one Linux box up and running .. working on graphic driver

Take a look at the sgfxi scripts I mentioned earlier in thread. They've worked flawlessly for me. Everything I needed was downloaded and installed in one shot. After installation, future driver updates are handled by a single command.

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

I tried update before booting into Vista. Then, booting today back I got that message. Cause it appears immediately after Win10 boot selection no way to update it into anything anymore.

Take a look at the sgfxi scripts I mentioned earlier in thread. They've worked flawlessly for me. Everything I needed was downloaded and installed in one shot. After installation, future driver updates are handled by a single command.

have the driver catalyst 15.9 installed on the machine .. Boinc does not recognize it .. talk about frustrating :(

---

have the driver catalyst 15.9 installed on the machine .. Boinc does not recognize it .. talk about frustrating :(

You'll need a new BOINC version with newer AMD recognition code. I've not too long ago sent in code with a lot of new AMD GPUs being recognized, so either you can build a new BOINC from code using branch 7.6, or look for new versions for your distro from people who build new versions (PPAs, package maintainers).

It'll have to be a version after 7.6.12

---

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

---

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

With my AMD cards I've always been able to fix that issue by placing a link to the opencl file in usr/lib. I've already posted this a couple of times but can't find it, so, here it is again.
If you don't have GKSU and Nautilus installed, install them;
sudo apt-get install gksu
sudo apt-get install nautilus

In the terminal run gksu nautilus, that will open a file browser as root.
Look in /usr/lib and see if you have a file named libOpenCL.so. You probably don't or it is named libOpenCL.so.1. Go to usr/lib/fglrx and make a link to libOpenCL.so.1, then move the link to usr/lib. Once the link is in usr/lib rename the link libOpenCL.so. If that doesn't work, make another link and name that one libOpenCL.so.1. With those links in usr/lib it should work.

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

I tried update before booting into Vista. Then, booting today back I got that message. Cause it appears immediately after Win10 boot selection no way to update it into anything anymore.

You could try setting the clock back to October 1st. Perhaps that would let it boot. Then you could updates the date & do an update maybe.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

I tried update before booting into Vista. Then, booting today back I got that message. Cause it appears immediately after Win10 boot selection no way to update it into anything anymore.

You could try setting the clock back to October 1st. Perhaps that would let it boot. Then you could updates the date & do an update maybe.

In other words cheat the liar :)
Well, I made DVD with latest Insider build yesterday - will try if direct recommended way of booting from such media will help...

Oh.... now it's another message. It says that "device is not connected". Win10 was on SDD and there were no issues with it prior launching fresh Win10 DVD boot....

EDIT: Power cycle and old message about expiration of winload returned. One another boot and Win10 "Repairing disk errors"... What it did with SDD on prev launch that errors appeared?...

EDIT2: great... SDD disappeared again after "repairing" Win10 DVD boot. Another power cycle and booting directly to Vista. It sees SSD as 2 partitions 118.8 RAW and 450MB "EISA configuration".
Before fiddling with Win10 it was single NTFS partition.

So, Windows 10 completely erased partition (and I really hope if it did not damage SDD on hardware level :/)

So, net loss so far: ~2 rarely accessed games, BOINC x64 data folder (can't find it on other partitions so probably it was there and lost) and Win10 x64 installation itself. Well, "definitely nothing to worry about M$ ways".

R-Studio accesses SDD OK, maybe it could salvage something...

(thanks god I didn't trust SDD stability enough to put anything vital there)