Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #182160
| From | Newyana2 <newyana@invalid.nospam> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Differences between versions |
| Date | 2025-02-09 19:43 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <vobi2m$t02t$1@dont-email.me> (permalink) |
| References | (1 earlier) <vo9atv$f7gk$1@dont-email.me> <voaab4$lion$1@dont-email.me> <vob73o$r2e5$1@dont-email.me> <vobap3$rnq8$1@dont-email.me> <vobdh2$s90q$1@dont-email.me> |
On 2/9/2025 6:25 PM, ...w¡ñ§±¤ñ wrote:
> Newyana2 wrote on 2/9/25 3:39 PM:
>> On 2/9/2025 4:35 PM, ...w¡ñ§±¤ñ wrote:
>>> Newyana2 wrote on 2/9/25 6:25 AM:
>>>>
>>>> 21H2 might work. I haven't tried it. When 22H2 wouldn't do an
>>>> update I just tried 20H2. I've tried 22H2 mounting the ISO and
>>>> booting from a rufused stick. The hardware doesn't seem to
>>>> be an issue. It just says it will only do a fresh install because
>>>> "Windows might be installed to the wrong location or I might
>>>> be trying to install an older OS."
>>>
>>>>
>>> Normally 20H2 to 22H2 does not require a clean install.
>>> - no significant hardware system requirements between the versions
>>> Conditions that might cause it:
>>> - Windows system image needs repair (DISM command line option)
>>> - Windows component store needs cleanup (DISM command line option)
>>> - Windows Update broken/corrupt
>>> - Windows Update engine out-of-date
>>> => May 2023 KB5026361 last release 20H2 update is required(LCU and
>>> SSU)to update to 21H2/22H2
>>> - Windows 20H2 does not have June 2023 KB5027389 stand-alone(not
>>> included with monthly LCU/SSU update) Windows 10 Compatibility
>>> Update(includes the Windows Recovery Update)and is deployed/installed
>>> separate update via Windows Update or the MSFT Catalog. Note June
>>> 2023 was also the first monthly update(LCU, SSU, SafeOS) that
>>> included the WinRE update for Win10 21H2 and 22H2
>>> - Device using Legacy MBR and not GPT(more common on older devices)
>>> where System partition is on the o/s partition
>>> - Device using GPT with no Recovery partition, or deleted Recovery
>>> partition, Windows partition not resizeable/shrink to free space to
>>> create WinRe partition, WinRE partition, if present, insufficient
>>> free space.
>>> - lesser issues(Graphics driver, Network driver outdated, stand-alone
>>> graphic card no longer supported or outdated driver); device has both
>>> onboard graphics and add-on graphics card with add-on enabled/onboard
>>> disabled[in some cases, BIOS/UEFI disabling the add-on and enabling
>>> the onboard will allow the 22H2 to be successfully installed]; 3rd
>>> party utilities that modify Windows; 3rd party AV/AM; end-user
>>> tweaking/removing main Windows integrated programs(Edge, Defender)
>>> - Windows Photos(rare case but a known issue) app package removed or
>>> uninstalled.
>>>
>>> Other routes to update
>>> - instead of using Windows Update or UBS media or ISO to update,
>>> use the the Win10 22H2 Update Assistant(download the exe from the
>>> Windows 10 Software Download site - 'Update Now' option.'
>>> - download exe file is 'Windows10Upgrade9252.exe
>>> => may be necessary to check the exe file's properties and unblock
>>> the exe and/or run the exe as admin
>>>
>>
>> Complicated. I tried the 20H2 ISO out of curiosity (what's already
>> on there) and that also refused to do an update. The update from
>> 7 to 20H2 was smooth, though at the time, 22H2 refused to do
>> anything but a clean install.
>>
>> I noticed that the system window pops up and then closes. So
>> something is not right. I ran SFC and DISM repairs. Still no luck
>> with the system window. It is using MBR. Though 22H2 doesn't seem
>> to be complaining about installing -- only refusing to update
>> rather than clean install.
>>
>> This computer also does have a graphics card added to
>> the onboard because the original predates HDMI and I needed
>> to be able to display on the monitor as well as running HDMI
>> to a TV. That graphics card is barebones. Something like a $35
>> NVidia, I think. (I don't play video games. Only pipe movies.)
>>
>> The complication here is that I don't have a problem with a clean
>> install but I expect it would lose the license, since Win7 -> 10 is no
>> longer a free update.
>>
>> It sounds like it's probably not worth trying to do much more.
>> Setup is not telling me what the issue is. And all the hardware issues
>> don't explain why even 20H2 refuses to install on top of itself. But
>> if I get bored I might re-run a Win7-> 20H2 update, then try 22H2
>> immediately, before tweaking 20H2.
>>
>>
>>
> Your symptom/issue is obviously not the first failure of 20H2 to 22H2 on
> a device(including those originally with Win7).
> - Those 'knowns' that I provided are almost everything I recall or
> have seen in my earlier 13 yrs in the MVP program, current MSFT
> listservers, AskWoody owner/admin/moderator patch lady(Susan B. - if she
> doesn't know about it, it didn't happen), and other sources.
>
> If you have verified:
> 1. the DISM Image and Component store routes show no corruption, no
> repair need, no component store cleanup
> 2. your 20H2 version is later than May 2023(the last released 20H2
> update was 19042.2965)Update Assistant route
> 3. your device has the June 2023 KB5027389 stand-alone(Compatibility
> update installed. (Fyi..the KB can be downloaded from the Catalog, if
> installed and already present, it will tell you not applicable or
> already installed)
>
> If the above are all ok, then try using the available online Update Now
> option to download and run the Upgrade Assistant - Windows10Upgrade9252.exe
>
Thanks, but that's way more trouble than this is worth.
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-08 19:26 -0500
Re: Differences between versions Paul <nospam@needed.invalid> - 2025-02-08 23:28 -0500
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-09 08:25 -0500
Re: Differences between versions MR <MR@invalid.invalid> - 2025-02-09 16:51 +0000
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-09 13:36 -0500
Re: Differences between versions Paul <nospam@needed.invalid> - 2025-02-09 15:23 -0500
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-09 16:18 -0500
Re: Differences between versions ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2025-02-09 14:35 -0700
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-09 17:39 -0500
Re: Differences between versions ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2025-02-09 16:25 -0700
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-09 19:43 -0500
Re: Differences between versions Paul <nospam@needed.invalid> - 2025-02-10 00:45 -0500
Re: Differences between versions Paul <nospam@needed.invalid> - 2025-02-10 02:30 -0500
Re: Differences between versions Newyana2 <newyana@invalid.nospam> - 2025-02-10 08:08 -0500
csiph-web