Can't upgrade Windows 7 to Windows 10. Getting 800704B8 3001A


  1. Posts : 2
    windows 7
       #1

    Can't upgrade Windows 7 to Windows 10. Getting 800704B8 3001A


    I've successfully upgraded two other windows 7 computers for our thrift stores. This third one is proving to be a challenge. I've tried installing from media creation tool twice, also from a USB. I've removed all antivirus programs. I've tried updating twice while in clean boot mode. Still having no luck. I'm sure there's an answer but I can't seem to find it. Any help would be appreciated.

    Ben

    Can't upgrade Windows 7 to Windows 10. Getting 800704B8 3001A-20190516_101644.jpg
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Fill out the System Specs in My Computer.
    Ram, Hard drive(s), Video, anything else plugged in?

    Also found similar problem here: Windows 10 upgrade problem - 0x80070428 - 0x3001A

    Check the log file in \$Windows.~BT\Sources\Panther\, see what error is indicated. If not sure post the log here.
      My Computers


  3. Posts : 2
    windows 7
    Thread Starter
       #3

    Here's the log file

    Attachment 234010

    - - - Updated - - -

    The only things plugged in are my mouse, keyboard, and monitor.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    Code:
    2019-05-16 19:31:04, Error                 SP     SPUpgradeSecurity: error in SceSetupSystemByInfName processing upgrade template. Error: 0x800704B8
    2019-05-16 19:31:04, Error                 SP     Cannot apply the security template for the new OS. Error: 0x800704B8
    2019-05-16 19:31:04, Error                 SP     Operation failed: Upgrade security. Error: 0x800704B8[gle=0x000000b7]
    2019-05-16 19:31:04, Error                 SP     Operation execution failed: 26. hr = 0x800704B8
    2019-05-16 19:31:04, Error                 SP     ExecuteOperations: Failed execution phase Pre First Boot. Error: 0x800704B8
    2019-05-16 19:31:04, Error                 SP     Operation execution failed.
    2019-05-16 19:31:04, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-FirstBoot operations. Error: 0x800704B8
    Found this identical failure and a fix: Windows 10 update fails with 0x80070002 0x3001a

    See if it works for you.

    If it doesn't help or causes other problems you can do a Clean install of Windows 10 then activate it using the Windows 7 key. Skip entering the key during install. Activate after install completes. I've found that works best. No idea why, it just does.

    Follow this tutorial: Windows 10 - Clean Install

    Drivers are available here: Support for Optiplex 7010
      My Computers


  5. Posts : 2
    W10 x64 Pro B1909
       #5

    How to fix Security Issue upgrading to W10 (Or even upgrades to W7 if you are still running that OS) Cannot apply the security template for the new OS. Error: 0x800704B8 3001A

    Note this is not for the non-technical user and does require manually editing the Registry so be certain to set a System Restore Checkpoint and backup your registry before you begin. Just sayin.

    Open a CMD prompt with administrator privileges
    run the command:

    secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose

    Look at secsrv log file in %windir$\security\logs and identify the specific registry entries with Access Denied issues. There may be lots of them. (We are not as concerned about entries where "...cannot find the file or path specified") You will need to check the permissions and set Owner for each Access Denied entry individually. Permissions/Ownership within a higher level entry may differ as they cascade from level to level so don't just set a top level entry to save the time of hitting each lower level entry individually. If you try to take shortcuts you may make Windows stop working altogether.

    Open Regedit, find each of those "Access Denied" entries, Rt Click and under Permissions check the Permissions are correct (use a functional PC to compare) and under Advanced set Owner for each noted reg entry with an Access Denied issue to what it is supposed to be. The entry should generally still show what the owner is ie: SYSTEM or Administrators Group, but again you may want to compare against a working PC. Then use " Replace owner on subcontainers and objects" to push the Correct Ownership down from that Access Denied entry through the nested reg entries. If you get errors doing so at a high level, keep drilling down until you are able to reset the ownership. Run the secedit command again and check the log file for more errors. Once you are able to run the secedit command cleanly, and you get to where there are no Access Denied errors you should be in good shape. Note you may have to run RegEdt32 if there are specific 32bit entry Access Denied issues that affect your situation. In my case there were still a few errors in the 32bit specific entries but those actually didn't affect my OS upgrade.

    Then you should be able to update Windows to the next version. In my case this was from W7 SP1 - W10 B1909.

    I believe in the case of the machines I'm seeing with this issue, malware had run some kind of permissions change policy against the registry and made a mess of the default permissions. Removing the malware long ago apparently didn't undo the permissions changes to the registry so I was left to cope with that manually. It's a bit tedious but if you absolutely cannot wipe and reload from scratch it might be worth doing. Worked for me.
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Never heard back from the OP @wecare so don't know if he/she fixed the problem or not.

    Your fix looks pretty good though, thanks for posting it. The secedit command is what the link I posted recommended as a fix, no additional registry work required.

    secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
    net localgroup users USER /add

    replace USER with your user.
      My Computers


  7. Posts : 2
    W10 x64 Pro B1909
       #7

    Yeah, it might have been your thread or one like it that provided the secedit cmd line I started with, think I found it out on MS Technet. I had noticed when I ran it that it claimed there were "Warnings that were safe to ignore" also my W7-W10 upgrade still failed with the same Security error. When I went to look at these so called "Warnings" in the logfile I noted that there were a ton of registry entries that showed Access Denied. I started checking Permissions and on the surface they seemed OK so I figured Ownership was likely an issue, once I sorted all that out the secedit cmd log file showed no more Access Denied errors and my W7-W10 upgrade was finally successful.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:30.
Find Us




Windows 10 Forums