Windows 10

Doc_N

2010 wrote: »

I`m using chrome 64 bit with no probs.

Quite the reverse for me - every so often (and several times a day) it hangs and can only be closed via Task Manager.

spud17

Richie-from-the-Boro wrote: »

HiYa Spud, a non-hypothetical answer, wear your speccy and you will be able to see all your Windows software [and hardware] details including your activated internal Serial Number. Best of luck.

HiYa RftB :beer:
I was just wondering how MS servers would cope with 2 licences assigned to one piece of equipment.

Speccy and similar are of no use with a clean install of Win 10, assuming you have already done an inplace upgrade.

Windows 10 is a bit new and different.
Once you've updated, your hardware is registered at Microsoft. If/when you do a clean install, there is no need to use any key, because the MS servers will activate based on your correct hardware being present.

2010

Doc_N wrote: »

Quite the reverse for me - every so often (and several times a day) it hangs and can only be closed via Task Manager.

Is that the 64 bit and if so does it happen on the 32 bit?

I found this use to happen if there was more than one tab open.

If you don`t use chrome what do you use?

Jivesinger

spud17 wrote: »

Windows 10 is a bit new and different.
Once you've updated, your hardware is registered at Microsoft. If/when you do a clean install, there is no need to use any key, because the MS servers will activate based on your correct hardware being present.

I've an idea that in earlier Windows versions, if a particular product key is being abused, then MS just block the key from activation.

In Windows 10, when everyone who upgraded has the same product key, they perhaps can't block the key any more, so maybe they might block a particular hardware signature... :shocked:

Fightsback

Jivesinger wrote: »

I've an idea that in earlier Windows versions, if a particular product key is being abused, then MS just block the key from activation.

In Windows 10, when everyone who upgraded has the same product key, they perhaps can't block the key any more, so maybe they might block a particular hardware signature... :shocked:

As TPM 2.0 is mandated for future hardware as of 2016 (1 year after RTM) that might give you clue as to their future plans.

spud17

Jivesinger wrote: »

I've an idea that in earlier Windows versions, if a particular product key is being abused, then MS just block the key from activation.

In Windows 10, when everyone who upgraded has the same product key, they perhaps can't block the key any more, so maybe they might block a particular hardware signature... :shocked:

I've not yet tried a clean install, only one update.
But from reading this forum, ignoring brand new copies of Win 10, it would appear that keys are no longer used, as long as the base OS is ok.

Richie-from-the-Boro

spud17 wrote: »

HiYa RftB :beer:
I was just wondering how MS servers would cope with 2 licences assigned to one piece of equipment.

Speccy and similar are of no use with a clean install of Win 10, assuming you have already done an inplace upgrade.

Windows 10 is a bit new and different.
Once you've updated, your hardware is registered at Microsoft. If/when you do a clean install, there is no need to use any key, because the MS servers will activate based on your correct hardware being present.

I initially did the upgrade and the O/S blew my drives SSD=C SSHD=D] to hell (more later). I reinstalled v8.1 slipstream USB telling it to format both drives and it validated me. I then v10 on a clean upgrade telling it to format both drives and it validated me again for the Win10 upgrade and then took windows DOT old subdirectory off with windows own clean up program remembering to click the critical 'system files' button.

I took the view that if I was ever to need another new install of v10 that using a slipstream USB install and validating with the number that speccy have me would be a very good 'test' and my initial start point. No I've never yet done it, and do not know anyone who has - but I would, in a menu of many longer options - try that first.

Win10 on my BIOS behaves like an out of control 'hoolie' with power saving, to include hidden hibernate and hidden USB timeout to sleep functions [example copying a 60 minute+ SATA2 T+ drive to a 2T Hybrid SATA3 via a USB caddy] also an unforgiving propensity to go to sleep [screen & drive] when it likes regardless of the fact that both are set to 'never'.

Most of the last para it turns out are well documented issues over the last 6 months, known by Microsoft and as yet unresolved in my case. Best of luck.

spud17

Richie-from-the-Boro wrote: »

I initially did the upgrade and the O/S blew my drives SSD=C SSHD=D] to hell (more later).

From my reading, this is what registers/activates your machine with Microsoft.
What you do after, up to a point, is irrelevant because you're already activated on MS servers with your machine's fingerprint.

Richie-from-the-Boro

As you wish spud17.

victor2

Richie-from-the-Boro wrote: »

Win10 on my BIOS behaves like an out of control 'hoolie' with power saving, to include hidden hibernate and hidden USB timeout to sleep functions [example copying a 60 minute+ SATA2 T+ drive to a 2T Hybrid SATA3 via a USB caddy] also an unforgiving propensity to go to sleep [screen & drive] when it likes regardless of the fact that both are set to 'never'.

Interesting comments above, especially regarding the power saving...
I am running W10 but using the Windows 7 Back up & Restore utility as File History is annoyingly inflexible for my needs. Anyway, the Win 7 backup is set as a task to wake up the computer out of hibernation, which it does. But it never goes back to sleep afterwards, which it should. The monitor does sleep though...
I am sorely tempted to restore Win 7 from the image backup I made before upgrading, but will stick with Win 10 for a bit longer as I support quite a few people using it, having actively encouraged them to ditch their Win 8's for it!