Windows 10: Error Upgrading to 1909

Discus and support Error Upgrading to 1909 in Windows 10 Ask Insider to solve the problem; Feature update to Windows 10, version 1909 - Error 0x800f0830 This is the error that i get over and over regardless of the things that I've tried to... Discussion in 'Windows 10 Ask Insider' started by /u/Existencex, Jan 26, 2020.

  1. Error Upgrading to 1909


    Feature update to Windows 10, version 1909 - Error 0x800f0830

    This is the error that i get over and over regardless of the things that I've tried to update.

    I booted into safe mode cleared the Software Distribution Folder.

    Restarted the Windows Update Service after changing it to Automatic.

    I have also tried Windows Update Assistant.

    Everything runs smoothly for the Windows Update Assistant up until the actual installation is happening after the restart, then i get a blue screen(not sure if there is something else i should possibly doing or an additional step i should be taking during the Update Assistant.)



    Hope someone out there has a solution for this! Thank you in advance!

    submitted by /u/Existencex
    [link] [comments]

    :)
     
    /u/Existencex, Jan 26, 2020
    #1

  2. Windows 10 1909 Causes Secondary Hard Drive to not be Recognized

    Installing the Windows 10 1909 Update causes my secondary hard drive to not be recognized.

    Steps to confirm issue:

    • Secondary drive not visible in Windows Explorer
    • Secondary drive not visible in device manager
    • Secondary drive not visible in disk manager

    Steps to replicate issue:

    • Installing 1909 update

    Steps to resolve issue:

    • Uninstall 1909 update

    Since updates can only be delayed for so long, an actual fix would be appreciated.
     
    Teknophile, Jan 26, 2020
    #2
  3. Video card or RAM need upgrading?

    Memtest: no errors after 10 hrs.
    I'm going to perform the Primetest, later on. Get back to you on that.
    I'm going to take it step by step, guys. I need to find the problem with this current computer. I might have to upgrade some components, so that it is still runnable. As for the new one, yes....i will build on it later. I need to find something decent 'gaming experience', all suggestions appreciated. THanks.
     
    itsmeitsme, Jan 26, 2020
    #3
  4. Ramhound Win User

    Error Upgrading to 1909

    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)
     
    Ramhound, Jan 26, 2020
    #4
Thema:

Error Upgrading to 1909

Loading...
  1. Error Upgrading to 1909 - Similar Threads - Error Upgrading 1909

  2. Windows 10 Upgrade Error. Cannot Upgrade Past 1909

    in Windows 10 Software and Apps
    Windows 10 Upgrade Error. Cannot Upgrade Past 1909: I ran SetupDiag: Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48SetupDiag version: 1.6.2107.27002 System Information: Machine Name = LUKE Manufacturer = Gigabyte Technology Co., Ltd. Model = AB350-Gaming 3 HostOSArchitecture = x64...
  3. Windows 10 Upgrade Error. Cannot Upgrade Past 1909

    in Windows 10 Installation and Upgrade
    Windows 10 Upgrade Error. Cannot Upgrade Past 1909: I ran SetupDiag: Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48SetupDiag version: 1.6.2107.27002 System Information: Machine Name = LUKE Manufacturer = Gigabyte Technology Co., Ltd. Model = AB350-Gaming 3 HostOSArchitecture = x64...
  4. Windows 10 Upgrade Error. Cannot Upgrade Past 1909

    in Windows 10 Gaming
    Windows 10 Upgrade Error. Cannot Upgrade Past 1909: I ran SetupDiag: Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48SetupDiag version: 1.6.2107.27002 System Information: Machine Name = LUKE Manufacturer = Gigabyte Technology Co., Ltd. Model = AB350-Gaming 3 HostOSArchitecture = x64...
  5. Upgrade to 1909 to 1709

    in Windows 10 Ask Insider
    Upgrade to 1909 to 1709: Good morning, I am trying to track down the patch that'll convert 1709 to 1909. I have tried searching the microsoft site with no luck. Can anyone point me to the patch please? We can't jump to 2004 due to compatibility issues. submitted by /u/heyyouITguy [link]...
  6. Preparing for 1909 upgrade

    in Windows 10 Installation and Upgrade
    Preparing for 1909 upgrade: I have recently began experiencing some OS issues in my i7-3630QM HP laptop, running Windows 10 Home x64 v1809. I am confident that it is an OS, not hardware issuelong boot times, cross linked files, logging out of account going to a black screen, certain updates not...
  7. 1909 upgrade problem

    in Windows 10 Installation and Upgrade
    1909 upgrade problem: After the upgrade to 1909 version for windows 10, file explorer launches when pc is turned on. How can I fix this? https://answers.microsoft.com/en-us/windows/forum/all/1909-upgrade-problem/58d7d6f6-51a2-4bcd-9ee7-9bbe44118bee
  8. Upgrade to 1909

    in Windows 10 Installation and Upgrade
    Upgrade to 1909: My Windows 10 laptop is running Windows version 1809. I have been told to upgrade to version 1909 but others have told me not to do this because there are problems with 1909. So what should I do?...
  9. Can't upgrade to 1909

    in Windows 10 Installation and Upgrade
    Can't upgrade to 1909: I did try to upgrade it from the Microsoft website which it doesn't work also so how will ur recommend me to do because ive no more idea what to do this method it doesn't work another method also doesn't work....
  10. 1903 to 1909 fails with Trying to upgrade to 1909, getting this error. 0x8e5e0152

    in Windows 10 Installation and Upgrade
    1903 to 1909 fails with Trying to upgrade to 1909, getting this error. 0x8e5e0152: SFC returns: C: \ WINDOWS \ system32> sfc / scannow Starting the system scan. This process will take some time. Beginning of the verification phase of the system scan. 100% complete verification. Windows resource protection found corrupt files but could not repair some...