Windows 7 Service Pack 1 fails with error code 0x8004a029


When installing Service Pack 1 on Windows 7 installations, you may enounter the following error code in the \Windows\Logs\CBS\CBS.log:  0x8004a029

The log snippet will look similar to the following:

2011-02-21 18:56:58, Error                 CSI    000006e1 (F) Done with generic command 60 (0x0000003c); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 41001 (0x0000a029) resulted in success? FALSE
    Process output: [l:73 [73]”Trying to install vpcnfltr …
..failed. Error code: 0x8004a029.
“][gle=0x80004005]

This is due to the filter limit in Windows 7.  To resolve this, do the following:

Option 1

Windows 7 is hard coded to allow 14 filter drivers, but the following registry sets the limit to 8 by default.  You can adjust the amount up to 14 or delete this key and it will be set to max of 14.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters 

Option 2

Remove some filter driver from ncpa.cpl –>  Chose network Properties –> Select and filter –> Uninstall

**Note** Not all networking filters are listed under ncpa.cpl, so application may need to be completely uninstalled (i.e. personal firewalls)

–Joseph

Comments (25)

  1. Are you highlighting the network key Jim?  It's located in that portion of the hive.

  2. Sorry Anshul, does this have something to do with SP1?

  3. @Pats, glad that worked for you.

  4. If you're seeing this problem Ed, check to see if you already have more than 14 filters.  If you do, then you need to remove some to get it to work.

  5. I didn't have this particular problem, but if I did, I don't know what I would have done without advice like this.

    In other words, good job 😉 I've only recently encountered your blog. I immediately subscribed to the RSS feed. Where else are you going to find someone who can decypher Component-Based Servicing?

  6. Start > Run > regedit.exe > navigate to the key above

  7. @Ping, if you highlight the Network hive you should see a MaxNumFilters value inside that branch of the registry.

  8. @GKH;  That's true for your machine.  However, CCS isnt always under CCS1, it can be any number depending on the installation.  

    @Andre;  Thanks for the FixIt link, I didnt realize the team put that out.

  9. Glad I can help out a little here and there 🙂

  10. Nope Ed, thats all on me.  I need to stop fatfingering things as I type them.  The proper applet is ncpa.cpl.  I couldnt have been more off if I had tried.  Thanks for picking that up.

  11. craig says:

    Option 1 has solved my issues.  Thanks a lot for the info!

  12. edonme says:

    It doesn´t work, still have the same problem

  13. Eric ver Linden says:

    Can you please explain to me how I get to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetworkMaxNumFilters?

    Please email me the answer, ericv1984@gmail.com

  14. jim says:

    I am using Windows 7 and MaxNumFilters is not there.

  15. Ed says:

    I don't see nacpl.cpl. Did a search. Nothing. Is it hidden?

  16. ASrock says:

    Really you must think this will work right you're a microsoft employee. Sorry to inform you this method doesn't work

  17. Linkan says:

    Thanks alot !!!!

    Solved my problem to update this from 8 to 14.

  18. Ping says:

    Hi Joseph, I just want to know what if the MaxNumberFilters is not in the registry under Networking hive. I'm pretty sure I went to the correct address but the folder is not there. Any suggestions?

  19. GKH says:

    what you write, is elsewhere: P

    check here:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSet001ControlNetworkMaxNumFilters (reg_DWORD) (8)

  20. Pats says:

    Worked like a charm. SP1 wasn't my issue, it was Virtual PC that failed but your solution applied for that as well. Thanks a mill!

  21. GerV says:

    well tried them all and some omre others, but not working. Any other ideas…?

  22. a_arb says:

    When i remote connect one system to another is message " THe stub  recieved bad data" I could not one system to other through net limiter 3.0

  23. JDUBB says:

    Many thanks for this tricky fix!!