J. P. Gilliver (John) wrote:
> On Mon, 28 Jun 2021 at 13:25:27, ...w¡ñ§±¤n <winstonmvp@gmail.com> wrote
> (my responses usually follow points raised):
>> Andy Burns wrote:
>>> J. P. Gilliver (John) wrote:
>>>
>>>> would I have to extract key(s?) from the 64bit machine [...]  before
>>>> nuking?
>>>  No, one of the improvements in win10, is that (once activated) the
>>> entitlement is stored on MS servers, so the same machine will be
>>> recognised and re-activated by any future Win10 re-install (with the
>>> home/pro level it had before).
>
> Thanks. So - if it ever comes to it, and I can only find a W10 64-bit
> machine, I can (assuming it's showing as activated, authorised, and so on)
> install from any W10 32-bit .iso of the same Home/Pro flavour I can find -
> no worries about version (2004, 21H1, or whatever) or whether the 64-bit
> was OEM or not?
Normally, yes.
When one purchases Windows 10 Retail, they are given a single product key
that applies to both 32 and 64 bit versions of Windows providing the
opportunity to install either version on a 64 bit architecture.

When one purchases an OEM version, they are given a single product key
that for the 32 bit ***or** 64 bit. I.e. OEM versions of Win10 only come
with 32 or 64 bit(media or download), not both(unlike Windows 10 retail).

To add to some of the variation, an OEM Win 10 device may have the product
key on firmware but that shouldn't be an issue, but it does at times offer
some confusion when folks ask and get answers on the topic.
=> The important part to remember is Windows 10 Product keys are edition
specific(Home, Pro) not bit specific.

>>>
>> Exception applies (not necessarily in JP's current statecase, but worthy
>> of mention)
>> Unless one makes a significant hardware change - primarily the mobo or cpu.
>
> In most cases, I don't think I'd consider it the "same machine" if I'd
> done that. (Academic anyway - it'd probably be a laptop, and I wouldn't
> even consider trying to change mobo or processor on one of those. The last
> desktop system I built was '98SElite [though made dual-boot to XP later].)
Not to many people replace mobos on Win10 laptops, those that do, unlike
the as-shipped device, afaik wouldn't have the system on chip product key
unless the mobo replace was provided by the OEM including instructions on
how to activate.(this would be a rare case for an OEM to ship a mobo to a
end-user).
>
>> In that case reactivation won't happen automatically unless the device
>> and license is linked to a MSFT Account which provides(and only
>> provides) the Troubleshooting option to 'acknowledge the hardware change
>> and reactivate'
>>
> Hmm.
:) If one wishes to dot all the i's and cross all the 't' then foresight
would apply. Set the machine up with an Microsoft Account Windows Logon.
If desired, that same MSA can be used to add another Windows logon(Local,
Admin). Once done, the original MSA now linked to the digital license
remains on MSFT servers(as well as the device's Local unlinked digital
license). Once linked, that MSA can be left on the device as a Windows
Logon or removed as a logon using the Local *Admin* logon.
- Mobo change later ? Setup the device with a clean install and use that
MSA for setup. If needed, use the provided(in Windows 10) MSA's
Troubleshooting option(internet connection necessary) to access the 'I
changed hardware on this device', reenter that same digitall linked MSA,
select the device('This is the device I'm using etc.), then select Activate'.

--
....w¡ñ§±¤n

On Mon, 28 Jun 2021 at 23:47:48, ...w¡ñ§±¤n <winstonmvp@gmail.com> wrote
(my responses usually follow points raised):
>J. P. Gilliver (John) wrote:
>> On Mon, 28 Jun 2021 at 13:25:27, ...w¡ñ§±¤n <winstonmvp@gmail.com>
>>wrote (my responses usually follow points raised):
>>> Andy Burns wrote:
>>>> J. P. Gilliver (John) wrote:
>>>>
>>>>> would I have to extract key(s?) from the 64bit machine [...] 
>>>>>before nuking?
>>>>  No, one of the improvements in win10, is that (once activated) the
>>>>entitlement is stored on MS servers, so the same machine will be
>>>>recognised and re-activated by any future Win10 re-install (with the
>>>>home/pro level it had before).
>> Thanks. So - if it ever comes to it, and I can only find a W10
>>64-bit machine, I can (assuming it's showing as activated,
>>authorised, and so on) install from any W10 32-bit .iso of the same
>>Home/Pro flavour I can find - no worries about version (2004, 21H1,
>>or whatever) or whether the 64-bit was OEM or not?
>Normally, yes.
>When one purchases Windows 10 Retail, they are given a single product
>key that applies to both 32 and 64 bit versions of Windows providing
>the opportunity to install either version on a 64 bit architecture.
>
>When one purchases an OEM version, they are given a single product key
>that for the 32 bit ***or** 64 bit. I.e. OEM versions of Win10 only
>come with 32 or 64 bit(media or download), not both(unlike Windows 10
>retail).

So OEM only _come with_ (media or otherwise) one bitness, but the
licence still _allows_ switching to the other bitness - it's just that
it's up to the user to actually find the necessary media (or whatever).
Right?
>
>To add to some of the variation, an OEM Win 10 device may have the
>product key on firmware but that shouldn't be an issue, but it does at
>times offer some confusion when folks ask and get answers on the topic.
> => The important part to remember is Windows 10 Product keys are
>edition specific(Home, Pro) not bit specific.
[]
>:) If one wishes to dot all the i's and cross all the 't' then
>foresight would apply. Set the machine up with an Microsoft Account
>Windows Logon. If desired, that same MSA can be used to add another
>Windows logon(Local, Admin). Once done, the original MSA now linked to
>the digital license remains on MSFT servers(as well as the device's
>Local unlinked digital license). Once linked, that MSA can be left on
>the device as a Windows Logon or removed as a logon using the Local
>*Admin* logon.

Thanks. I'll store that!

> - Mobo change later ? Setup the device with a clean install and use
>that MSA for setup. If needed, use the provided(in Windows 10) MSA's
>Troubleshooting option(internet connection necessary) to access the 'I
>changed hardware on this device', reenter that same digitall linked
>MSA, select the device('This is the device I'm using etc.), then select
>Activate'.
>
>
(-:
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

We all have an expiry date on us, but it's usually in a difficult place to
read. - Steve Hague in UMRA, 2020-11-3

Sailfish wrote:
> ...w¡ñ§±¤n graced us with on 6/28/2021 9:06 AM:
>> Sailfish wrote:
>>> J. P. Gilliver (John) graced us with on 6/27/2021 7:51 PM:
>>>> Has there been any indication of whether Windows 11 will be 64-bit
>>>> only? [Or even 128-bit (-:]
>>>
>>> Many will need a whole new setup, apparently.
>>>
>>> //
>>> That potentially rules out millions of existing Windows 10 devices from
>>> upgrading to Windows 11 with full support, and even devices like
>>> Microsoft’s own Surface Studio 2 which the company is still selling
>>> right now for $3,499. Older devices that aren’t officially supported
>>> will be met with a warning during the Windows 11 install that the
>>> upgrade is not recommended, but the OS should still install.
>>> //
>>> https://www.theverge.com/2021/6/25/22549725/microsoft-windows-11-cpu-support-tpm-hardware-requirements
>>
>>
>> That article was updated which appears to dispel the 'older device
>> warning...OS should install'
>> //
>> Originally, Microsoft noted that CPU generation requirements are a “soft
>> floor” limit for the Windows 11 installer, which should have allowed
>> some older CPUs to be able to install Windows 11 with a warning, but
>> hours after we published this story, the company updated that page to
>> explicitly require the list of chips above.
>> //
>>
> Precisely.
>
:)
Then thanks for confirming that the original quoted content about a
'warning and the W11 o/s should still install', no longer applies atm and
maybe forever.

--
....w¡ñ§±¤n

Windows 11 is zero (0) bits due to not existing.

Lucifer wrote:
> Windows 11 is zero (0) bits due to not existing.

I got yer 64 bits right here.

https://i.postimg.cc/J4yGKf3d/GoesTo11.gif

And that menu is definitely Apple-flavored.

Not having the Start in the corner, takes some
getting used to.

Paul

In article <sbi2qd$3e8$1@dont-email.me>, Paul <nospam@needed.invalid>
wrote:

>
> Not having the Start in the corner, takes some
> getting used to.

or just move it back.

<https://www.howtogeek.com/737830/how-to-move-the-taskbar-icons-to-the-l
eft-on-windows-11/>

<https://www.howtogeek.com/wp-content/uploads/2021/06/win11_taskbar_choo
se_left.jpg>

On Wed, 30 Jun 2021 11:32:27 -0400, Paul <nospam@needed.invalid>
wrote:

>Lucifer wrote:
>> Windows 11 is zero (0) bits due to not existing.
>
>I got yer 64 bits right here.
>
> https://i.postimg.cc/J4yGKf3d/GoesTo11.gif
>
>And that menu is definitely Apple-flavored.
>
>Not having the Start in the corner, takes some
>getting used to.
>
> Paul

Someone will program a "move" modification for it.

KenW

In article <v2jpdg5n33pg8dpp40i50asn0trqf1cp2a@4ax.com>, KenW
<ken1943@invalid.net> wrote:

> >Not having the Start in the corner, takes some
> >getting used to.
> >
>
> Someone will program a "move" modification for it.

microsoft already did.

On 2021-06-30 10:32 a.m., Paul wrote:
> Lucifer wrote:
>> Windows 11 is zero (0) bits due to not existing.
>
> I got yer 64 bits right here.
>
>    https://i.postimg.cc/J4yGKf3d/GoesTo11.gif
>
> And that menu is definitely Apple-flavored.
>
> Not having the Start in the corner, takes some
> getting used to.
>
>    Paul

In the taskbar settings there is a feature that lets you set it center
or left edge.

Rene

On Wed, 30 Jun 2021 16:31:25 -0500, Rene Lamontagne <rlamont@shaw.ca>
wrote:

>On 2021-06-30 10:32 a.m., Paul wrote:
>> Lucifer wrote:
>>> Windows 11 is zero (0) bits due to not existing.
>>
>> I got yer 64 bits right here.
>>
>>    https://i.postimg.cc/J4yGKf3d/GoesTo11.gif
>>
>> And that menu is definitely Apple-flavored.
>>
>> Not having the Start in the corner, takes some
>> getting used to.
>>
>>    Paul
>
>
>In the taskbar settings there is a feature that lets you set it center
>or left edge.
>
>Rene
>

I want the right edge where I have had it since FOREVER

KenW