fbl_impressive Enterprise 10130 - Error 0x80246017

 fbl_impressive Enterprise 10130 - Error 0x80246017

Now I m on build 10125.

Thanks

 

Question Info


Last updated September 6, 2018 Views 16,856 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi Biliboy,

Welcome to Microsoft Community.

This issue needs advanced troubleshooting and for that we have dedicated experts with advanced tools and permissions to help you with this type of issues. I suggest you to post the same in Microsoft TechNet forum for further assistance with this issue.

https://social.technet.microsoft.com/Forums/en-US/home?forum=WinPreview2014General

Please get back to us for any other support on Windows. We will be glad to help you again.

Thank You

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I was on 10125 with my Sandy Bridge Extreme last night and this morning 10130 is fine. Gee am I surprised!!!

Renee

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

  • Disable (preferrably uninstall) your Antivirus utility before attempting the upgrade.
  • Restart a few times and try again.
  • Disable General USB Devices (example - Smart Card Reader). 
  • If you are using a SCSI hard disk, make sure you have drivers available for your storage device on a thumdrive and it is connected. During Windows 10 setup, click the Custom Advanced Option and use the Load Driver command to load the appropriate driver for the SCSI drive. If this does not work and setup still fails, consider switching to a IDE based hard disk.
  • Do a clean boot and try again.
  • If you are upgrading using the .ISO file, disconnect from the Internet during setup, if you are connected by LAN (Ethernet) or Wi-Fi, disable both and attempt setup again. 
  • If you are updating through Windows Update, when the download reaches 100% disconnect from the Internet LAN (Ethernet) or Wi-Fi and proceed with the installation.
  • If that does not work, try using the .ISO file to upgrade if possible.
  • If you are connected to a domain, switch to a local account
  • If you have any external devices attached to the machine, disconnect them (example, gaming controllers, USB keys, external hard disc, printers, non-essential devices).

    If you are installing Windows 10 using Windows Update, try the following:

    1. Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” from the menu.

    2. Stop the BITS, Cryptographic, MSI Installer and the Windows Update Services. To do this, type the following commands at a command prompt. Press the “ENTER” key after you type each command.

                               net stop wuauserv

                               net stop cryptSvc

                               net stop bits

                               net stop msiserver

    3. Now rename the SoftwareDistribution and Catroot2 folder. You can do this by typing the following commands in the Command Prompt. Press the “ENTER” key after you type each command.

                              ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

                              ren C:\Windows\System32\catroot2 Catroot2.old

    4. Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Typethe following commands in the Command Prompt for this. Press the ENTER key after you type each command.

                            net start wuauserv

                            net start cryptSvc

                            net start bits

                            net start msiserver

    5. Type Exit in the Command Prompt to close it and then restart the computer.

    Try updating again

Best,
Andre
Windows Insider MVP
MVP-Windows and Devices for IT
twitter/adacosta
groovypost.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Still get the same error.  I really think it's a server side issue since so many people are having this problem.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Ok I had the same error trying to install 10122 and now with 10130.

fbl_impressive Enterprise 10130 - Error 0x80246017

How do I fix this?

I tried all of the above and it still does not install.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Well, you could wait until Microsoft releases the .ISO image for build 10130 and use that to do a build to build upgrade.
Best,
Andre
Windows Insider MVP
MVP-Windows and Devices for IT
twitter/adacosta
groovypost.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

?

As an Fast Ring insider, no ISO builds will be available officially.

Also, builds that become available for Fast Ring users may never go to Slow Ring (when ISO's are issued).

So waiting for an official ISO from Microsoft is not a valid solution or even reasonable.

Also, this error code is question is widespread among Insiders.  Currently Microsoft hasn't developed an official solution.  The same error code on previous updates could be addressed through Registry edits or Powershell and/or Command Prompt commands.

Solution for Insiders (assumes you are a competent tester):

* Download an install an unofficial ISO

* Live with a prior Build

* Wait until Microsoft issues a solution (which will likely happen this week since Build 10130 was released on a Friday.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

When you start working at Microsoft in the Operating System Group, I will start taking your word as gospel:

If Build 10130 looks good in the Fast ring, we will look at pushing it to the Slow ring and releasing ISOs.

Source:

http://blogs.windows.com/bloggingwindows/2015/05/29/announcing-windows-10-insider-preview-build-10130-for-pcs/

This is why 10122 was never officially released as a .ISO:

We won’t be pushing Build 10122 to the Slow ring due to a bug impacting upgrades from Windows 7 and Windows 8.1.

I was able to do a build to build upgrade using an unofficial ISO from build 10074

Best,
Andre
Windows Insider MVP
MVP-Windows and Devices for IT
twitter/adacosta
groovypost.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

SuperSite for Windows Article:

According to Microsoft, Windows Update should've set the registry keys back to the proper value, but failed to do so.  .

Here's what to do…

  1. Open the registry editor and navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
  2. Locate BranchName and make sure it shows: FBL_AWESOME1501. If it doesn't, change it.
  3. Locate ThresholdRiskLevel and change it to: low
  4. Find ThresholdInternal and delete it.
  5. Find ThresholdOptedIn and delete it.

Pat

As a responsible member of the community, please mark the reply that has resolved your issue. Thank you.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

New builds simply say fbl_impressive.  Supersite instructions from build 9926 (not enterprise)

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.