Groups > alt.comp.os.windows-11 > #16462

Re: W12 release?

From	...w¡ñ§±¤ñ <winstonmvp@gmail.com>
Newsgroups	alt.comp.os.windows-11
Subject	Re: W12 release?
Date	2025-01-22 13:40 -0700
Organization	windowsunplugged.com
Message-ID	<vmrl4d$16nr7$1@dont-email.me> (permalink)
References	(1 earlier) <lva5tfF2h2qU3@mid.individual.net> <vmoq8r$a62o$1@dont-email.me> <vmouka$blpq$1@dont-email.me> <vmptt2$p6t4$1@dont-email.me> <vmq33q$qp7k$1@dont-email.me>

Show all headers | View raw

Paul wrote on 1/21/25 11:27 PM:
> On Tue, 1/21/2025 11:58 PM, ...w¡ñ§±¤ñ  wrote:
>> Paul wrote on 1/21/25 1:04 PM:
>>> On Tue, 1/21/2025 1:50 PM, T wrote:
>>>> On 1/21/25 10:04 AM, s|b wrote:
>>>>> On Mon, 20 Jan 2025 20:15:13 -0800, T wrote:
>>>>>
>>>>>> I do not suppose M$ will release W12 in time for the
>>>>>> October 2024 end of support for W10?
>>>>>
>>>>> What about hardwire requirements? Every W10 I've tested didn't have the
>>>>> right hardware for an upgrade to W11, let alone W12.
>>>>>
>>>>
>>>>
>>>> I am trying to get around my PCI people on W10 having
>>>> to upgrade all the hardware for W11 just to have W11
>>>> expire in two years again
>>>>
>>>> Be nice to just do one hardware & software upgrade
>>>> instead of two
>>>
>>> When you needed it, the W12 might not be "ripe".
>>>
>>> Staggered is the right answer.
>>>
>>> Do you remember how long it took to release 24H2 ?
>>> It took forever. They might "finish" W12, then have
>>> an extended testing period.
>>>
>>>      Paul
>>>
>> :)
>> If there's a 25H2 then its EOS would be 2027
>>   - which would likely yield W12 in Oct 2026.
>>
>> Similar to Win10 to Win11, a lot of the bits(old and new) are already in the former!
>>   i.e. W12 testing is probably occurring right now in 24H2 and even more so in Build 27774(Canary).
> 
> So your hypothesis, is that the new OS won't have any content.
> 
> Right now, there is only one certified NPU, Recall hasn't shipped,
> and they've just announced that a tranche of developers have
> been "sent to do AI". Like, sent this week kind of thing.
> 
> And they're re-inflating Clippy in the basement of the Microsoft building.
> 
>     Paul
> 

:) I didn't specifically state 'won't have any content'

Only that bits for the next have routinely been included in the current. 
Even more so for the annual release of the same version.

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

Thread

W12 release? T <T@invalid.invalid> - 2025-01-20 20:15 -0800
  Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-21 02:46 -0500
    Re: W12 release? T <T@invalid.invalid> - 2025-01-20 23:51 -0800
    Re: W12 release? "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-01-25 20:29 +0800
  Re: W12 release? Andy Burns <usenet@andyburns.uk> - 2025-01-21 08:46 +0000
    Re: W12 release? T <T@invalid.invalid> - 2025-01-21 00:56 -0800
  Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-21 03:18 -0700
  Re: W12 release? "s|b" <me@privacy.invalid> - 2025-01-21 19:04 +0100
    Re: W12 release? T <T@invalid.invalid> - 2025-01-21 10:50 -0800
      Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-21 15:04 -0500
        Re: W12 release? Me <me@mars.invalid> - 2025-01-22 02:27 +0000
          Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:33 -0800
          Re: W12 release? Daniel70 <daniel47@eternal-september.org> - 2025-01-30 21:11 +1100
            Re: W12 release? Andy Burns <usenet@andyburns.uk> - 2025-01-30 10:48 +0000
              Re: W12 release? knuttle <keith_nuttle@yahoo.com> - 2025-01-30 07:17 -0500
                Re: W12 release? Daniel70 <daniel47@eternal-september.org> - 2025-02-01 21:02 +1100
            Re: W12 release? T <T@invalid.invalid> - 2025-01-30 13:43 -0800
              Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-30 19:29 -0500
                Re: W12 release? T <T@invalid.invalid> - 2025-01-30 17:27 -0800
                Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-30 21:54 -0500
                Re: W12 release? T <T@invalid.invalid> - 2025-01-30 20:04 -0800
              Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-31 11:10 -0700
                Re: W12 release? T <T@invalid.invalid> - 2025-01-31 11:10 -0800
                Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-01 01:42 -0700
                Re: W12 release? T <T@invalid.invalid> - 2025-02-01 10:02 -0800
                Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-01 12:54 -0700
            Re: W12 release? "Alan K." <alan@invalid.com> - 2025-01-30 17:07 -0500
              Re: W12 release? T <T@invalid.invalid> - 2025-01-30 14:27 -0800
              Re: W12 release? Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-01-31 22:31 +0000
            Re: W12 release? Ali Mirza <ali.mirza@yahoo.com> - 2025-01-31 01:25 +0000
              Re: W12 release? T <T@invalid.invalid> - 2025-01-30 18:44 -0800
              Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-31 11:16 -0700
                Re: W12 release? T <T@invalid.invalid> - 2025-01-31 11:11 -0800
        Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-21 21:58 -0700
          Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-22 01:27 -0500
            Re: W12 release? ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-01-22 13:40 -0700
        Re: W12 release? "s|b" <me@privacy.invalid> - 2025-01-22 19:13 +0100
        Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:32 -0800
      Re: W12 release? Chris <ithinkiam@gmail.com> - 2025-01-22 08:12 +0000
        Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:35 -0800
          Re: W12 release? Chris <ithinkiam@gmail.com> - 2025-01-23 07:54 +0000
  Re: W12 release? Newyana2 <newyana@invalid.nospam> - 2025-01-22 09:07 -0500
    Re: W12 release? Paul <nospam@needed.invalid> - 2025-01-22 14:57 -0500
      Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:43 -0800
    Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:42 -0800
  Re: W12 release? Sam E <no.email@here.invalid> - 2025-01-22 17:43 +0000
    Re: W12 release? T <T@invalid.invalid> - 2025-01-22 14:43 -0800

csiph-web