Windows 10: Many upgrade attempts for 1909 to no avail - same error from minidumps

Like many others I cannot upgrade Win 10 pro 1909 to 2004 or 20H2.

Started out with message from Microsoft that support would end for my version - click click - upgrade assistant - failure!

Running a bare bones Dell Optiplex 7010


Cores 4

Threads 8

Name Intel Core i7 3770

Code Name Ivy Bridge

Package Socket 1155 LGA

Technology 22nm

Specification Intel Core i7-3770 CPU @ 3.40GHz

Family 6

Extended Family 6

Model A

Extended Model 3A

Stepping 9

Revision E1/L1

Instructions MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, Intel 64, NX, AES, AVX

Virtualization Not supported

Hyperthreading Supported, Enabled

Bus Speed 99.3 MHz

Stock Core Speed 3400 MHz

Stock Bus Speed 100 MHz

Average Temperature 30 °C


with Logitech Keyboard & Mouse and Brother printer both USB attached.


Tried all the solutions so far, sfc, dism, media creation tool, direct iso update, disabled all non microsoft services - all seem to fail around 60% of install phase 2+hrs into the process!!

Minidumps have the same caused by message of ntoskrnl.exe+1c3ab0. 1st dump was 20H2 iso update and 2nd was 2004 iso update.



Last bit of setupact.log from 2004 update is

------------------------------------------------------

2021-03-26 20:20:34, Info CSI 00001014 Begin executing advanced installer phase 9 index 83 sequence 90

Old component: [l:0]''

New component: [l:140 ml:141]'HyperV-VmChipset, Culture=neutral, Version=10.0.19041.153, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'

Install mode: delta

Smart installer: false

Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}

Installer name: 'Events'

2021-03-26 20:20:34, Info CSI 00001015 Performing 1 operations as follows:

0 LockComponentPath: flags: 0 comp: {l:16 b:8a983a019f22d7015c2000006c25cc07} pathid: {l:16 b:8a983a019f22d7015d2000006c25cc07} path: [l:98]'\??\X:\Windows\WinSxS\amd64_hyperv-vmchipset_31bf3856ad364e35_10.0.19041.153_none_b32940cfeb827fac' pid: 256c starttime: 132612778207400884

2021-03-26 20:20:34, Info CSI 00001016@2021/3/27:00:20:34.648 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};HyperV-VmChipset, version 10.0.19041.153, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};5751us

2021-03-26 20:20:34, Info CSI 00001017 End executing advanced installer sequence 90

Completion status: S_OK



2021-03-26 20:20:34, Info CSI 00001018 Begin executing advanced installer phase 9 index 0 sequence 0

Old component: [l:0]''

New component: [l:0]''

Install mode: delta

Smart installer: true

Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}

Installer name: 'Events'

2021-03-26 20:20:34, Info CSI 00001019 Registry root HKLM\Software: HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SOFTWARE\



2021-03-26 20:20:34, Info CSI 0000101a Registry root HKLM\System: HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SYSTEM\

------------------------------------------------Nothing after the line above----------

Don't know what Phase 9 index 0 is but somewhere I saw that it may have something to do with an overworked clocked processor.

Does anyone have any ideas?

Thanks

:)

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.

 

Completely missing Dot Net in Windows 10 -1909?

.NET Framework is built-into Windows 10 version 1903 and Windows 10 version 1909. It is not possible for at least this version of the .NET Framework to be installed.

The error you have received, is likely due to the fact the application you are attempting to use, is specifically trying to target a version of the .NET Framework you don't have installed. I suggest using official Microsoft tool to download a Windows 10 version 1909 ISO. You can use the Media Creation Tool and/or the Upgrade Assistant. Windows ISO Downloader was only recently updated to support .NET Framework 4.8 on November 8th 2019. If you were not using Version 8.22, and would like to still use the tool, you need to download that version.

RaymondCC .NET Detector looks at registry keys that are created when you install .NET Framework. It does not support the .NET Framework version that are included with Windows 8.0+

The built-in version of the .NET Framework for Windows 10 version 1903 was .NET Framework 4.8

.NET Framework 4.5+ has never been located in the list of Windows Features for any version of Windows. The lack of .NET Framework 3.5 is likely due to your WinSxS directory not containing it.

You can install .NET Framework 3.5 if you run the same command you ran, but provide a source, to the components you need.

This is due to the fact the .Net Framework 4.8 is already installed on Windows 10 version 1903 and Windows 10 version 1909. .NET Framework 4.8 is an in-place upgrade to .NET Framework 4.5

This normally only happens when you have moved vital folders like the user's profile to a non-standard location.

Your inability to install .NET Framework 3.5 is extremely easy to fix and likely the reason your unable to run the third-party application. Perform the following steps to solve that problem.

1. Download a Windows 10 version 1909 ISO
   
2. Mount the ISO within Windows 10
   
3. Run the following command, the command assumes, the drive letter assigned to the virtual mount is D:
   
   • DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs
     

Source: Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM)

 

User.000 issue after updating to 1909

I'm one of the many people suffering from issues with user profiles after applying Update 1909 to Windows 10. I've read all the threads I can find on the topic here and have followed the suggestions, all to no avail. Any other thoughts are appreciated.

After applying Update 1909, the ProfileImagePath was changed to c:\users\User.000
One file that was always in use and couldn't be removed was left in c:\users\User (can't recall or find the exact file now), so I could never rename or remove the c:\user\User directory.

I followed the multiple suggestions from Brink and others:

• Rebooted at least 6 times
• Enabled hidden Administrator
• Booted into Safe Mode
• Changed ProfileImagePath
• Tried to rename c:\users\User but couldn't because a file was still in use
• Copied all data from c:\users\User.000 into c:\users\User
• Rebooted and had temporary profile
• Followed steps in Brink tutorial to change ImageProfilePath; rebooted with no change
• Restored using Restore Point from before Update 1909 - returned to single profile state (User.000)
• Removed each update that was installed individually and rebooted after each update removal - profile state never changed
• After all updates were removed, repeated the steps above with hidden Administrator, changing profile, etc. - same issue with file in use in c:\users\User
• Followed all steps above with hidden Administrator but without copying files from User.000 to User - same results

Any suggestions are greatly appreciated!