Windows (update not clean install) has failed to initialise the working directory


jimbo45

jimbo45

Well-known member
Pro User
VIP
Local time
1:51 AM
Posts
4,918
Location
Hafnarfjörður IS
OS
Windows XP,7,10,11 Linux Arch Linux
Hi folks
Clean install of insider build 22623.1020 from ISO worked perfectly.

However trying to do an update from build 22621.900 I get the following error :

Screenshot_20221202_114217.png


Now I'm getting totally confused as to what builds can be updated, what are current and what are in the various available builds. I can't believe how Ms has made this such a real dogs dinner (and that's being hard on the poor canines).

Incidently build 22621.900 reports "Up to date" from Windows update



What we need is a spreadsheet with current builds which are updateable to the latest available version of each. Otherwise this is becoming an unmanageable project even with a load of VM's.

I don't want to keep re-installing Windows from scratch over and over again. My arch linux system just updates on a daily basis or whenever with just a single command pacman -Syu and even if there's a new kernel it updates in seconds !!!!

I know there are test and alpha builds and so I'm not afraid of getting the odd defect or so - but the current mess is just bonkers.


There seem 3 main streams -- 22000, 226XX, and 25252 with a load of builds within those. But what goes with what ????

Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
jimbo45 said:
Clean install of insider build 22623.1020 from ISO worked perfectly.

However trying to do an update from build 22621.900 I get the following error...
Click to expand...
Wher did you get the ISO? If it was UUP dump then it may not be MS's fault. It's not unknown for an ISO built by UUP dump to have 'oddities' like this.

jimbo45 said:
Now I'm getting totally confused as to what builds can be updated, what are current and what are in the various available builds....

...There seem 3 main streams -- 22000, 226XX, and 25252 with a load of builds within those. But what goes with what ????
Click to expand...

Any build should be upgradable to a higher one.

22000 is 21H2 and available in the Release Preview and General Availability channels.
22621 is 22H2 and available in the Beta, Release Preview and General Availability channels.
22623 is 22H2 and available in the Beta channel.
25XXX is only found the Dev channel.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.

    My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Dev, and Canary builds (and a few others) as a native boot .vhdx.

    My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro 24H2, Hyper-V host machine.
Bree said:
Wher did you get the ISO? If it was UUP dump then it may not be MS's fault. It's not unknown for an ISO built by UUP dump to have 'oddities' like this.



Any build should be upgradable to a higher one.

22000 is 21H2 and available in the Release Preview and General Availability channels.
22621 is 22H2 and available in the Beta, Release Preview and General Availability channels.
22623 is 22H2 and available in the Beta channel.
25XXX is only found the Dev channel.
Click to expand...
Thanks --really appreciate your usually helpful answers etc.

So I assume it was my fault in the sense that build 22621if from the general availability channel can't be upgraded to 22623 - but needs a clean install. Ms are still IMO making a bit of a meal of this.

I got my iso from UUPDUMP which is currrently working OK again (relief)!.

Thanks again @Bree

Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
You must log in or register to reply here.

Similar threads

Failed to initialize Windows Sandbox.Error 0x80070002. Cannot find the specified file.
Replies
1
Views
5K
cereberus
cereberus

Latest Support Threads

Latest Tutorials

Back
Top Bottom