none
Windows 7 backup error, unable to do system backups

    Question

  •  

    I recently upgraded my system  from vista 64 to windows 7, and when I tried to back up received the following error message:
    The backup application could not start due to an internal error.
    The specified service does not exist as an installed service. (0x80070424)
    (1) There is a "Windows Backup" in Services.msc.
    (2) "wbengine" folders are  missing from the Control Set folders in Hkey_local_machine

    Tuesday, October 27, 2009 3:16 AM

Answers

  • 1. Input Services.msc in Start --- Search to start Services box. Check if Windows Backup service is Started and set as "Manual". If not, change it to Manual and click Start to start it. You can stop and then restart it, reboot to see the result.

    2. If issue still exists, find this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    Export it to Desktop as an REG file (as a backup) and delete the key. Then download this file, rename it to wbengine.reg and double click on it to import to Registry.

    Then restart the computer to see the result.


    Tuesday, October 27, 2009 6:19 AM
    Moderator

All replies

  • 1. Input Services.msc in Start --- Search to start Services box. Check if Windows Backup service is Started and set as "Manual". If not, change it to Manual and click Start to start it. You can stop and then restart it, reboot to see the result.

    2. If issue still exists, find this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    Export it to Desktop as an REG file (as a backup) and delete the key. Then download this file, rename it to wbengine.reg and double click on it to import to Registry.

    Then restart the computer to see the result.


    Tuesday, October 27, 2009 6:19 AM
    Moderator
  • Thank You Shaon. Your instructions fixed the problem and I'm now able to Backup my system.
    Thanks Again
    Tuesday, October 27, 2009 10:26 PM
  • I came across your solution after doing some internet searching. It worked! Thank you.
    Friday, October 30, 2009 1:58 AM
  • 1. Input Services.msc in Start --- Search to start Services box. Check if Windows Backup service is Started and set as "Manual". If not, change it to Manual and click Start to start it. You can stop and then restart it, reboot to see the result.

    2. If issue still exists, find this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    Export it to Desktop as an REG file (as a backup) and delete the key. Then download this file, rename it to wbengine.reg and double click on it to import to Registry.

    Then restart the computer to see the result.



    I cannot find this key in regedit (or at least this specific key), there is no entry listed for wbengine in services?
    • Proposed as answer by Jerold.o Saturday, February 13, 2010 2:25 AM
    Monday, November 2, 2009 5:48 AM
  • Hi Limey72,

    If there is no mistake when you trying to find the key, the key is missing from your computer which is the cause of the issue.

    Import the key with steps i provided and reboot to see the result.
    Monday, November 2, 2009 8:50 AM
    Moderator
  • I downloaded the file (rt clicked and downloaded to desktop) then renamed it (rt clicked and renamed) and double clicked - on rebooting I still get the error message  0x80070424
    • Proposed as answer by BadPugs Saturday, December 26, 2009 9:29 PM
    Monday, November 2, 2009 5:04 PM
  • I have tried this fix several times to no avail.  No matter what I do the key is always missing from the registry.
    Monday, November 2, 2009 5:47 PM
  • Same problem here. Fresh install of Win 7 Pro x64, with all driver and Windows updates installed. Tried the fix above about five different times, still no wbengine folder in the registry. It's like it was never installed on our machines during Windows setup.
    Monday, November 2, 2009 6:32 PM
  • I gave up and just dragged the wbengine.reg desktop file into the registry path described above. I restarted my PC and ran Windows Backup without error messages! It's running now. I'll post if I have further issues. Nearly went crazy looking for this solution. Never had backup issues with Vista! 
    • Proposed as answer by frederick70 Monday, November 2, 2009 6:43 PM
    Monday, November 2, 2009 6:42 PM
  • I gave up and just dragged the wbengine.reg desktop file into the registry path described above. I restarted my PC and ran Windows Backup without error messages! It's running now. I'll post if I have further issues. Nearly went crazy looking for this solution. Never had backup issues with Vista! 

    How do you drag it into the registry path?
    Monday, November 2, 2009 6:59 PM
  • Open the registry to the path (see above), and leave the window open, but not filling the whole screen. Click on the desktop file you downloaded (see above) and drag it to where it should be in the registry. This worked for me after I ran the file several times and that didn't help. Now Backup actually starts, and actually runs (still running right now, no errors).

    Monday, November 2, 2009 7:33 PM
  • Hi limey72,

    If you cannot put the key into registry key, it may be caused if there is no permission to access the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services key. Check the permission option of the key.
    Tuesday, November 3, 2009 1:52 AM
    Moderator
  • Sorry to be so dumb Shaon - but how would I check that?
    Tuesday, November 3, 2009 7:33 AM
  • Right click on the Services key, choose Permission. Click Add, type Everyone and click OK to add it to the list.

    Then highlight Everyone, check the box "Full Control" and click OK.

    Now everyone has permission on modify the key. Try add the wbengine key again.
    Wednesday, November 4, 2009 2:45 AM
    Moderator
  • Open the registry to the path (see above), and leave the window open, but not filling the whole screen. Click on the desktop file you downloaded (see above) and drag it to where it should be in the registry. This worked for me after I ran the file several times and that didn't help. Now Backup actually starts, and actually runs (still running right now, no errors).


    I tried this, but am unable to "drag" it into the registry path....everytime I try it just fades as I drag it over and nothing happens..
    Thursday, November 5, 2009 6:13 AM
  • 10 days ago I built a new system, with Windows 7 Professional, and the next day I tried to backup, and received the following error message:
    The backup application could not start due to an internal error.
    The specified service does not exist as an installed service. (0x80070424) 

    If I reload Windows from the Disc using the repair option, the backup option will then work, for maybe 1 hour to 1 day

    After finding this post, I checked the registry, when I get the above error there is no "wbengine"  in the RegistryControl Set folders in Hkey_local_machine.
    After reloading windows. the
    "wbengine"  is in the RegistryControl Set folders in Hkey_local_machine.

    So I started to check out what was happening, after loading windows, I found the
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    I Exported it to Desktop as an REG file (as a backup)

    I then run System Machanic Pro v9, and this said you have registry problems, so I let it fix them, Then checking the registry the "wbengine" had been removed, and the above error error appeared.
    I then imported the the saved reg file, and the backups works.

    So in my case the "System Machanic pro v9 is causing my problem,
    How this helps someone.
    Thursday, November 5, 2009 2:09 PM
  • I have the same problem since i installed windows 7 pro final version upgrade, nothing posted here worked, but i found an easy workaround and it WORKS. if you have any other computer running vista or win 7 (doesn't matter version) go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine, export the key to a flash drive, then on the troubled computer import the key, reeboot and thats it, back up working.
    Friday, November 6, 2009 12:56 AM
  • The problem causing this at least in my case is system mechanic pro ver.9, i ran a registry clean and the problem re-appeared, think i will fire an email to system mechanic.
    • Proposed as answer by JohnHollinger Sunday, November 8, 2009 3:02 AM
    Friday, November 6, 2009 3:31 AM
  • Had the same problem with System Mechanic & emailed Iolo. They didn't say why they are removing the wbengine key in Win7 but offered this workaround:
    http://www.iolo.com/customercare/kbarticle.aspx?ID=KBA-01980 . It seems to be working ok for me now. Good Luck.
    Sunday, November 8, 2009 3:13 AM
  • This worked for me as well.  thanks Sharon. 

    I wonder why MS does not fix this.
    Sunday, November 8, 2009 5:55 AM
  • I'm glad I found this forum. I have the exact same problem. Last week, I got my new Digital Storm with Windows 7 64 bit. I put System Mechanic on first. It said I had registry problems. I thought that strange, but I thought if it crashed my system I could just reinstall from my Digital Storm disk. Nothing seemed to happen. Then I went through a couple of days of shear pain trying to deactivate/activate/install Mathematica, Photoshop, Lightwave, City Navigator/Microsoft Office. When I finished, I thought, "I never want to go through that again!" I tried to make a system image, and I got the error mentioned above. There was no copy of wbengine anywhere on my computer. Fortunately, tech support at Digital Storm is excellent. The tech found a copy of this entry on the internet, took control of my machine and fixed my problem. I emailed System Mechanic twice, but got no replies. Yesterday, I emailed them and told them to take me off automatic updates (I had been a loyal customer for years). They emailed me back an apology, took me off automatic updates, but did not explain this problem.
    Wednesday, November 11, 2009 10:48 PM
  • I suspected System Mechanic was the cause all along. I don't have Pro, just the regular version. Now I'm wondering what other registry "errors" it fixes every time it runs.
    Saturday, November 14, 2009 2:58 AM
  • Ronnie,
    The solution you gave worked immediately.  Although, evertime I restart my computer I have to redo the change to the registry.  I have Windows 7 64 bit, and a Dell computer.  Any ideas? 

    Thanks.
    Monday, November 23, 2009 5:49 PM
  • Ronnie,
    The solution you gave worked immediately.  Although, evertime I restart my computer I have to redo the change to the registry.  I have Windows 7 64 bit, and a Dell computer.  Any ideas? 

    Thanks.

    Hi,

    If the solution can help on your issue, it means the Windows Backup service or its registry key is affected by any program on your computer each time to reboot the computer. As System Mechanic is mentioned as one of the possible cause, is it installed on your computer? If not, is there any registry cleaner or third party backup program installed? Try disable them to see the result.

    If issue still exists, you can create a new topic to contniue discuss the issue.
    Tuesday, November 24, 2009 3:09 AM
    Moderator
  • Installed W7 64 Professional bit a few days ago. I also got the same Windows Backup error message.
    I also happen to have System Mechanic version 9 and had previously  run it. I also had run REGCURE.
    Took advantage of the early free support service from Microsoft and called the problem in.
    The rep found that WBengine was missing. He tried to merge  the missing code into the Registry
    but failed. Finally, he asked me to boot up Windows from the HD, then run a Windows Repair (using the W7 installation CD).
    That did the trick.

    However, afterwards, I found that my WIndows 7 Upgrade Version  was no longer Activated and it would not Activate when I re-entered
    my Licence Key. I called Microsft again. The rep had me run a Windows Upgrade but, afterwards, I still could not Activate.

    So, I used the Telephone Activation procedure and that worked fine.

    I have e/mailed a query to IOLO about the possibility  that System Mechanic 9 deleted WBEngine. haven't heard back yet.
    Meanwhile, just in case, I won't run the Registry Repair portion of SM.

    If anyone else can confirm that SM 9 is the culprit, please le us know.
    Wednesday, November 25, 2009 2:59 AM
  • Yes I can confirm that System manager 9 will remove the Wbengine from the registry, this has been a ongoing problem.
    Find this key in the registry  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine
    then Export it to Desktop as an REG file (as a backup). This can then always be imported back into the registry.
    System manager can be configered to ignore this file when it checks the registry
    Good luck, dexter
    Wednesday, November 25, 2009 9:29 PM
  • Thanks for your help on this one :)

    I could not double click the reg file as it opens up notepad and I also could not drag it into the registry.

    What I ended up doing was a file import to the Services folder.

    From the top menu in the registry - File --> Import (making sure to have the services folder selected beforehand).
    Tuesday, December 1, 2009 5:55 PM
  • I just ran System Mechanic version 9.5.0 with Tune-up Definitions version 3.0.29.0 and WBengine stayed in the registry as it should.  Maybe Iolo has fixed this??
    Tuesday, December 1, 2009 9:12 PM
  • Hello Jay-Bo

    To import the backup reg file

    Open  "regedit" select import from the file menu, select the backup reg item, and it will put back into registry

    Cheers Dexter
    Tuesday, December 1, 2009 9:35 PM
  • Hello Jay-Bo

    I have just checked the latest version of System machanic 9.0.5 tune-up Definitions version 3.0.29.0

    And this is still removing "wbengine" from the registry, so be careful

    Jay-Bo, have you still got this key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine" excluded from being checked ?

    As soon as you remove this exclution key, the wbengine reg file will be removed, and you wil get this error,

    The backup application could not start due to an internal error.
    The specified service does not exist as an installed service. (0x80070424).

    so be carefull People

    Dexter
    Tuesday, December 1, 2009 10:04 PM
  • Hi Dexter,

    I didn't exclude the key - Maybe it just gets removed when you do a deep analysis?? 

    Anyways, I sent a file to Iolo for their tech guys to look at.

    Hope they find an answer.

    Jason
    Wednesday, December 2, 2009 7:47 AM
  • I emailed Iolo and sent them a link to this page, stating that they could lose a lot of customers if they didn't do something. I finally got two emails back. They gave me the same advice that was stated above on how to exclude wbengine. That made me happy enough to install System Mechanic 9.5, but I still don't have enough faith in the product to actually run a registry cleaning. I am hoping some of you with more experience than me will report when this problem is fixed. I would have a lot more faith in System Mechanic if they had admitted the problem and issued a warning. As I stated, I spent at least 2-3 days installing very expensive programs on this new computer. It was a total nightmare that I don't want to repeat--because of deactivation/activation. I now have a system image, but I have never tried it to see if it will restore my programs and system. I wish I had found this problem earlier. I would have then been happy to play Russian Roulette with System Mechanic and Windows 7 64 bit if all I had to do was reinstall the system image from Digital Storm.
    Thursday, December 3, 2009 6:43 AM
  • I just ran SM again and it tried to remove the wbengine, so I excluded it for now.
    Thursday, December 3, 2009 7:57 AM
  • I received an email from Iolo this morning about an update.  So I installed the update - 9.5.1 and removed the exclusion on the wbengine.

    I ran SM twice today and both times it has left wbengine alone. 
    Friday, December 4, 2009 6:19 AM
  • Hello Jay-Bo

    I can confirm that the latest System Manager Pro v9.5.1 Dated 4th Dec has now solved the problem of removing the "wbengine" from the registry.

    Thanks to all concerned.

    Dexter (merry Christmas)
    Friday, December 4, 2009 5:21 PM
  • Hey everyone... I just registered here cos I noticed lots of people have this same problem. None of the solutions here worked for me, so i had to be a little more creative... And I fixed it, just now.

    I'm running Windows 7 x64, but I'm quite sure this works on any version of Vista / 7.

    What I've done was, I re registered all my DLLs from Windows\System32 folder. So now we're gonna make this same batch program. I found this all over the internet, so I'm really not sure who is the original author. I used it to fix other dll related issues, and apparently it fixed this one as well. This is how you do it.

    1. Run Command Promt as Administrator.

    2. You should end up in your system32 directory.. otherwise navigate there manualy.

    3. Type, or paste this in the command propt: DIR *.dll /s /b > c:\regdll.bat

    4. Next, type or paste this: notepad regdll.bat

    5. This opens up notepad with a long list of DLLs. Now go to edit/replace (ctrl+h).
        Type "C:\" In the Find what field (without quotation marks).
        Type "C:\Windows\System32\Regsvr32.exe /s C:\" in the Replace with field (also without quotation marks).
        Click Replace all.

    6. Save the file, and go back to command prompt. Type "cd\" (without quotation marks) and hit enter.

    7. Type regdll.bat, and wait for the batch program to finish. It could take a while, and if you get any error messags, don't worry, just do whatever it takes to get rid of them (ok, cancel, whatever).

    And that should be it! You don't have to restart your computer (at least I didn't). Try running a backup now, and see how it goes.


    NOTE on step 5: for some strange reasons this batch script would stop when ever it reached a line with some unix (?) DLLs. This is why I would recommend that you also replace every "unix" word with something like, I dunno, XXXXX, or whatever makes absolutely no sense. You can skip this, but if you notice the script got stuck with some of these DLLs, do it.
    Monday, December 14, 2009 10:14 PM
  • This is al way, way, way to complicated to those of us who do not understand the lingo. I have the same problem. Will one of you guys who have some influence or maybe work for Microsoft please tell them to do an update for this problem? I'll bet lots of people have this problem but can't fix it on their own.
    Thursday, December 24, 2009 2:20 AM
  • To fix the missing registry entry, Here is what you do! Type in search(regedit), Double click regidit, this will let you enter the registry!          BE VERY----VERY--- VERY--- CAREFUL!!!!!        TAKE YOUR TIME!      Open(Witch MEANS Expand) HKEY_LOCAL_MACHINE, Open system, Open currrent control set, pick any registry name in the a"s.  Now right click it, name it,wbengine and save it to your desk top. All this does is copy it to your desktop with a different name! Now , we are going to delete and replace the information in side the new registry key on your desk top! Right click the new key named(wbengine) and open with note pad!  Select all and delete: Replace with:                                                                                                                                                                                                                                               Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine]

    "DisplayName"="@%systemroot%\\system32\\wbengine.exe,-104"

    "ErrorControl"=dword:00000001

    "ImagePath"=hex(2):22,00,25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,\

    6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\

    00,77,00,62,00,65,00,6e,00,67,00,69,00,6e,00,65,00,2e,00,65,00,78,00,65,00,\

    22,00,00,00

    "Start"=dword:00000003

    "Type"=dword:00000010

    "Description"="@%systemroot%\\system32\\wbengine.exe,-105"

    "ObjectName"="localSystem"

    "ServiceSidType"=dword:00000001

    "RequiredPrivileges"=hex(7):53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,\

    00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\

    65,00,00,00,53,00,65,00,42,00,61,00,63,00,6b,00,75,00,70,00,50,00,72,00,69,\

    00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4d,00,61,00,6e,00,\

    61,00,67,00,65,00,56,00,6f,00,6c,00,75,00,6d,00,65,00,50,00,72,00,69,00,76,\

    00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,73,00,74,00,\

    6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,\

    00,53,00,65,00,53,00,79,00,73,00,74,00,65,00,6d,00,45,00,6e,00,76,00,69,00,\

    72,00,6f,00,6e,00,6d,00,65,00,6e,00,74,00,50,00,72,00,69,00,76,00,69,00,6c,\

    00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,69,00,\

    74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\

    00,65,00,54,00,61,00,6b,00,65,00,4f,00,77,00,6e,00,65,00,72,00,73,00,68,00,\

    69,00,70,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\

    00,65,00,53,00,68,00,75,00,74,00,64,00,6f,00,77,00,6e,00,50,00,72,00,69,00,\

    76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00

    "FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\

    00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00                                                                                                                                                     

    Saturday, December 26, 2009 9:54 PM
  • Now close and save. Now double click the new registry entry and add to your registry! YES     Now restart your computer Thanks BadPugs
    Saturday, December 26, 2009 9:56 PM
  • On the "open current control set" I'm lost when you talk about "pick any registry name in the a's" - can you explain this more please!
    Saturday, January 2, 2010 8:36 PM
  • After you open your Registry(regedit), expand      HKEY_LOCAL_MACHINE    NEXT EXPAND SYSTEM,  NEXT EXPAND CURRENTCONTROLSET,  NEXT EXPAND services:  UNDER SERVICES    ARE: "ALL" YOUR REGISTRY ENTRIES FOR "ALL" YOUR PROGRAMS ON YOUR COMPUTER! NOW JUST POINT AND LEFT, CLICK ANY ONE, OF THE ENTRIES(NAMES), NOW RIGHT CLICK IT, CHOOSE THE WORD (EXPORT) THE PAGE THAT IT BRINGS UP WILL BE,(EXPORT REGISTRY FILE),ALL      EXPORT REGISTRY FILE     IS A COPY OF THE FILE YOU CHOSE TO EXPORT!:    AT THE NEAR BOTTOM OF THE PAGE, IT HAS A EMPTY SPACE: MARKED FILE NAME: TYPE      wbengine       IN THE EMPTY SPACE ,THIS WILL GIVE IT A NEW NAME YOU NEED!      NOW CHOOSE DESKTOP AND SAVE IT(ALL YOU ARE DOING IS SAVING A COPY OF A REGISTRY KEY FILE, AND RENAMING IT TO THE FILE NAME YOU NEED!                 Now , we are going to delete and replace the information in side the new registry key FILE you need  on your desk top! Right click the new key FILE named    wbengine   and open with note pad!  Select all on edit, AT THE TOP, and THEN go back and   delete: Replace the info: with the info i last posted!  Left click, high lite, copy then paste it!                                    Now close and save. Now double click the new registry entry(by double clicking it it, it adds it to your registry)  it may say allow or yes,  do one!    Now restart your computer                    Sorry!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!                                    Thanks BadPugs
    Monday, January 4, 2010 1:57 AM
  • I did all that, dble clicked on the registry entry on desktop and saw no "allow, or yes", rebooted and am still unable to do a backup!

    And I am unable to find the wbengine key in the registry.....it is still on the desktop...

    Monday, January 4, 2010 3:26 AM
  • If you want I can email you the registry key!        My Email is: badlyonspugs@sbcglobal.net
    Wednesday, January 6, 2010 12:24 AM
  • Good fix.
    But I dont understand  I Ihave checked the new and the ods reg and This is the same???
    But the result is there
    Thank you

    Config: Acer: Aspire X3200, AMD Phenom 9550 ( 32-bit Quad core ), 4 Gb RAM, MB: Acer WMCP78M, Chipset: Nvidia; GeForce 9400 (GF8200 + GF 9200) MCP78PV
    Tuesday, February 2, 2010 3:27 PM
  • Here is the file you need.   just copy it into wordpad or notepad.  Change the .txt to .reg and resave it. then Import it into Regedit.
    Windows Registry Editor Version 5.00




    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine]
    "DisplayName"="@%systemroot%\\system32\\wbengine.exe,-104"
    "ErrorControl"=dword:00000001
    "ImagePath"=hex(2):22,00,25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,\
      6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
      00,77,00,62,00,65,00,6e,00,67,00,69,00,6e,00,65,00,2e,00,65,00,78,00,65,00,\
      22,00,00,00
    "Start"=dword:00000003
    "Type"=dword:00000010
    "Description"="@%systemroot%\\system32\\wbengine.exe,-105"
    "ObjectName"="localSystem"
    "ServiceSidType"=dword:00000001
    "RequiredPrivileges"=hex(7):53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,\
      00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\
      65,00,00,00,53,00,65,00,42,00,61,00,63,00,6b,00,75,00,70,00,50,00,72,00,69,\
      00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4d,00,61,00,6e,00,\
      61,00,67,00,65,00,56,00,6f,00,6c,00,75,00,6d,00,65,00,50,00,72,00,69,00,76,\
      00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,73,00,74,00,\
      6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,\
      00,53,00,65,00,53,00,79,00,73,00,74,00,65,00,6d,00,45,00,6e,00,76,00,69,00,\
      72,00,6f,00,6e,00,6d,00,65,00,6e,00,74,00,50,00,72,00,69,00,76,00,69,00,6c,\
      00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,69,00,\
      74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\
      00,65,00,54,00,61,00,6b,00,65,00,4f,00,77,00,6e,00,65,00,72,00,73,00,68,00,\
      69,00,70,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\
      00,65,00,53,00,68,00,75,00,74,00,64,00,6f,00,77,00,6e,00,50,00,72,00,69,00,\
      76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
    "FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
      00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00

    Saturday, February 13, 2010 2:24 AM
  • Hi,

     

    This worked for me. What causes this key to be missing from the Registry?

     

    Eric

    Tuesday, July 27, 2010 4:23 AM
  • The problem is that once you fix it that way, then run SM with the Registry cleaner running it the webengine thingy in Registry will probably disappear again.  I know my current version of SM takes it out every time.
    Thursday, July 29, 2010 12:09 AM
  • Because it is not a Microsoft problem.  It is a System Mechanic Problem..
    Thursday, July 29, 2010 12:15 AM
  • Here is what System Mechanic Says:

     

    Excluding items from the System Mechanic Registry Optimizer

    This article applies to:

    System Mechanic 7

    System Mechanic 7 Professional

    System Mechanic 8

    System Mechanic 8 Professional

    System Mechanic 9

    System Mechanic 9 Professional

    Step-by-step Instructions

     

    Open System Mechanic

    From the main navigation panel select Toolbox (or Tools)>Individual Tools to display a list of tool categories.

    From the category list select Repair Problems, locate the Repair Registry Problems tool, then click the corresponding Start button.

    From the Operation Mode tab of the wizard, select Custom Optimization and Repair located under the Advanced heading, then click Next.

    From the Tests tab clear the Invalid Folder and Filename References box, click Next.

    From the Options tab, click Add located under the Exclusions heading.

    From the Edit Exclusion window, Browse to the registry key or value you wish to exclude, then click Exclude Selected Key/Value. When you are finished click OK.

    Click Next to begin searching for problems.

    Inspect detected items to ensure that a needed item is not marked for repair.

    To exclude an entry from future searches, ensure Expert Mode is turned on by clicking Tools>Expert Mode. Then highlight the entry you wish to exclude and click Tools>Exclude selected from future searches.

    Repair or exclude entries as desired, when you are finished, click Exit.

    _end of instructions__

    Now,  once you have eliminated the ability of SM to remove the reg key, then go to the IOLO website and download the latest update which is 9.5.1,  I believe.   Run the install for the new version.  This new version is supposed to no longer take webengine key out anymore.

    Then, if you want to bother, you can remove the exclusion. (Good Luck!)  I would just leave it there to play it safe.

    jerold

    • Proposed as answer by Jerold.o Thursday, July 29, 2010 12:23 AM
    Thursday, July 29, 2010 12:18 AM
  • Chances are good then that at some point you used System Mechanics Repair system telling it to only open .reg files as notepad files.  SM tells you that allowing the opening of Registry files is a Security Risk and suggests you only allow opening them in notepad.  I fell for this one myself.  Anyway, once you do that, reg files no longer work like their supposed to.  Regedit can't fix them because SM won't allow it anymore. 
    Thursday, July 29, 2010 12:28 AM
  • This is what System Mechanic Says to do.  Assuming you were running System Mechanic which caused the problem:

    Excluding items from the System Mechanic Registry Optimizer

    This article applies to:

    System Mechanic 7

    System Mechanic 7 Professional

    System Mechanic 8

    System Mechanic 8 Professional

    System Mechanic 9

    System Mechanic 9 Professional

    Step-by-step Instructions

     

    Open System Mechanic

    From the main navigation panel select Toolbox (or Tools)>Individual Tools to display a list of tool categories.

    From the category list select Repair Problems, locate the Repair Registry Problems tool, then click the corresponding Start button.

    From the Operation Mode tab of the wizard, select Custom Optimization and Repair located under the Advanced heading, then click Next.

    From the Tests tab clear the Invalid Folder and Filename References box, click Next.

    From the Options tab, click Add located under the Exclusions heading.

    From the Edit Exclusion window, Browse to the registry key or value you wish to exclude, then click Exclude Selected Key/Value. When you are finished click OK.

    Click Next to begin searching for problems.

    Inspect detected items to ensure that a needed item is not marked for repair.

    To exclude an entry from future searches, ensure Expert Mode is turned on by clicking Tools>Expert Mode. Then highlight the entry you wish to exclude and click Tools>Exclude selected from future searches.

    Repair or exclude entries as desired, when you are finished, click Exit.

    ____________end of instructions________

    Now, I am told SM has put out a new updated version.  9.5.1 or some such.

    Apparantly that new version or update will fix the problem of deleting the reg file (webengine)  BUT, you still will have to put it back in before you update because if you don't it won't be there and the updated version won't put  the file back. YOU have to do that.  I would think that putting the webengine regfile back, then updating to the new version, will fix the problem permanently.

    • Proposed as answer by Jerold.o Thursday, July 29, 2010 12:45 AM
    Thursday, July 29, 2010 12:38 AM
  • Did you do all of the steps below?

    Excluding items from the System Mechanic Registry Optimizer

    This article applies to:

    System Mechanic 7

    System Mechanic 7 Professional

    System Mechanic 8

    System Mechanic 8 Professional

    System Mechanic 9

    System Mechanic 9 Professional

    Step-by-step Instructions

     

    Open System Mechanic

    From the main navigation panel select Toolbox (or Tools)>Individual Tools to display a list of tool categories.

    From the category list select Repair Problems, locate the Repair Registry Problems tool, then click the corresponding Start button.

    From the Operation Mode tab of the wizard, select Custom Optimization and Repair located under the Advanced heading, then click Next.

    From the Tests tab clear the Invalid Folder and Filename References box, click Next.

    From the Options tab, click Add located under the Exclusions heading.

    From the Edit Exclusion window, Browse to the registry key or value you wish to exclude, then click Exclude Selected Key/Value. When you are finished click OK.

    Click Next to begin searching for problems.

    Inspect detected items to ensure that a needed item is not marked for repair.

    To exclude an entry from future searches, ensure Expert Mode is turned on by clicking Tools>Expert Mode. Then highlight the entry you wish to exclude and click Tools>Exclude selected from future searches.

    Repair or exclude entries as desired, when you are finished, click Exit.

    Thursday, July 29, 2010 12:39 AM
  • Do this instead.

    Excluding items from the System Mechanic Registry Optimizer

    This article applies to:

    System Mechanic 7

    System Mechanic 7 Professional

    System Mechanic 8

    System Mechanic 8 Professional

    System Mechanic 9

    System Mechanic 9 Professional

    Step-by-step Instructions

     Then, before running SM again, update to the newest version (9.5.1 or whatever) 

    Open System Mechanic

    From the main navigation panel select Toolbox (or Tools)>Individual Tools to display a list of tool categories.

    From the category list select Repair Problems, locate the Repair Registry Problems tool, then click the corresponding Start button.

    From the Operation Mode tab of the wizard, select Custom Optimization and Repair located under the Advanced heading, then click Next.

    From the Tests tab clear the Invalid Folder and Filename References box, click Next.

    From the Options tab, click Add located under the Exclusions heading.

    From the Edit Exclusion window, Browse to the registry key or value you wish to exclude, then click Exclude Selected Key/Value. When you are finished click OK.

    Click Next to begin searching for problems.

    Inspect detected items to ensure that a needed item is not marked for repair.

    To exclude an entry from future searches, ensure Expert Mode is turned on by clicking Tools>Expert Mode. Then highlight the entry you wish to exclude and click Tools>Exclude selected from future searches.

    Repair or exclude entries as desired, when you are finished, click Exit.

    Thursday, July 29, 2010 12:41 AM
  • OK, now go to IOLO website and download the newest update (9.5.1 or somesuch).  Then install it BEFORE you run SM Again!!!

    With the new version, I am told, that the webengine problem is fixed.

    Thursday, July 29, 2010 12:49 AM
  • I believe you will find that System Mechanic takes it out when you run the reg cleaner tool.  Don't know why but they have apparantly fix it with a newly available version update # 9.5.1.  Once that is installed and the webengine key is back up and running, SM won't take it out anymore. (or so I am told.)
    Thursday, July 29, 2010 1:08 AM
  • Jerold,

     

    Sadly, I use Iolo's Dell PC TuneUp program, which is essentially the same thing (I believe) as SystemMechanic. But, there have been no new updates to Dell PCTuneUp from Iolo lately at all.

    Right now I set it so that during the registry cleaning it ignores anything to do with missing services etc etc.

     

    Regards,

    Eric

    Wednesday, September 8, 2010 4:15 AM
  • I gave up and just dragged the wbengine.reg desktop file into the registry path described above. I restarted my PC and ran Windows Backup without error messages! It's running now. I'll post if I have further issues. Nearly went crazy looking for this solution. Never had backup issues with Vista! 

    How do you drag it into the registry path?

    The above download and drag worked for me fine after I downloaded the wbengine reg file and renamed. Rebooted , started Backup windows and got the prompts . So , ready to go, many thanks
    Thursday, March 31, 2011 4:07 AM
  • 1. Input Services.msc in Start --- Search to start Services box. Check if Windows Backup service is Started and set as "Manual". If not, change it to Manual and click Start to start it. You can stop and then restart it, reboot to see the result.

    2. If issue still exists, find this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    Export it to Desktop as an REG file (as a backup) and delete the key. Then download this file, rename it to wbengine.reg and double click on it to import to Registry.

    Then restart the computer to see the result.


    Dowloaded the File and Double Clicking won't Import it to the Registry.
    Monday, January 30, 2012 2:41 PM
  • I gave up and just dragged the wbengine.reg desktop file into the registry path described above. I restarted my PC and ran Windows Backup without error messages! It's running now. I'll post if I have further issues. Nearly went crazy looking for this solution. Never had backup issues with Vista! 
    Where is the Registry Path?
    Monday, January 30, 2012 3:06 PM
  • "D. J. Casper. _" wrote in message news:c497d0aa-4907-4bce-896b-527cbd86588e...
    1. Input Services.msc in Start --- Search to start Services box. Check if Windows Backup service is Started and set as "Manual". If not, change it to Manual and click Start to start it. You can stop and then restart it, reboot to see the result.

    2. If issue still exists, find this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wbengine

    Export it to Desktop as an REG file (as a backup) and delete the key. Then download this file, rename it to wbengine.reg and double click on it to import to Registry.

    Then restart the computer to see the result.


    Dowloaded the File and Double Clicking won't Import it to the Registry.
     
    You have to RENAME it first!
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, January 30, 2012 4:38 PM
  • After struggles, found this solution and it work perfectly as directed!!  Thank you.  The key was missing so the export was not an issue, but the rest of the solution, importing the key was!
    • Edited by Mike 8803 Wednesday, November 28, 2012 1:42 AM
    Wednesday, November 28, 2012 1:40 AM
  • Hey everyone... I just registered here cos I noticed lots of people have this same problem. None of the solutions here worked for me, so i had to be a little more creative... And I fixed it, just now.

    I'm running Windows 7 x64, but I'm quite sure this works on any version of Vista / 7.

    What I've done was, I re registered all my DLLs from Windows\System32 folder. So now we're gonna make this same batch program. I found this all over the internet, so I'm really not sure who is the original author. I used it to fix other dll related issues, and apparently it fixed this one as well. This is how you do it.

    1. Run Command Promt as Administrator.

    2. You should end up in your system32 directory.. otherwise navigate there manualy.

    3. Type, or paste this in the command propt: DIR *.dll /s /b > c:\regdll.bat

    4. Next, type or paste this: notepad regdll.bat

    5. This opens up notepad with a long list of DLLs. Now go to edit/replace (ctrl+h).
        Type "C:\" In the Find what field (without quotation marks).
        Type "C:\Windows\System32\Regsvr32.exe /s C:\" in the Replace with field (also without quotation marks).
        Click Replace all.

    6. Save the file, and go back to command prompt. Type "cd\" (without quotation marks) and hit enter.

    7. Type regdll.bat, and wait for the batch program to finish. It could take a while, and if you get any error messags, don't worry, just do whatever it takes to get rid of them (ok, cancel, whatever).

    And that should be it! You don't have to restart your computer (at least I didn't). Try running a backup now, and see how it goes.


    NOTE on step 5: for some strange reasons this batch script would stop when ever it reached a line with some unix (?) DLLs. This is why I would recommend that you also replace every "unix" word with something like, I dunno, XXXXX, or whatever makes absolutely no sense. You can skip this, but if you notice the script got stuck with some of these DLLs, do it.

    This worked for me. The registry fix would not work. After hours of searching order has been restored.
    Saturday, December 1, 2012 8:06 PM