Share via

The description for Event ID 7003 from source Netwtw14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. I

EA Chalama balagopala 0 Reputation points
2026-01-19T20:19:45.46+00:00

Issue Description: When the Public Firewall Profile is enabled, the laptop is unable to access the Internet. However, when the Public Firewall Profile is disabled, Internet connectivity works without any issues.

 

Investigation Summary: Upon analysis, we identified that an inherent and invisible firewall policy named “lpacsensendr” is blocking DHCP and DNS traffic, which results in Internet disruption. This typically occurs when the policy store becomes corrupted.

 

Currently, the only documented resolution appears to be a full OS reinstallation, which is not an acceptable solution in this scenario. We need to determine the root cause and identify a fix that does not involve reinstalling the operating system.

Windows for business | Windows 365 Enterprise
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 30,935 Reputation points Independent Advisor
    2026-01-21T07:48:50.4133333+00:00

    Hello EA Chalama balagopala,

    I wanted to follow up on the status of the "lpacsensendr" firewall block. As previously outlined, the most direct resolution involves backing up and then deleting the FirewallRules and RestrictedServices subkeys located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy, followed immediately by a netsh advfirewall reset. This sequence forces the Base Filtering Engine (BFE) to discard the corrupted policy store and regenerate a clean default state, thereby removing the invisible rule blocking your DHCP and DNS traffic without requiring a full OS reinstallation.

    If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

    VP

    0 comments
  2. VPHAN 30,935 Reputation points Independent Advisor
    2026-01-19T20:52:12.02+00:00

    Hi EA Chalama balagopala,

    You will need to modify the registry directly to clear the corrupted policy cache. Open the Registry Editor (regedit.exe) as an Administrator and navigate to the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy. Right-click the FirewallPolicy key and export it to a safe location as a backup. Once backed up, locate and delete the following subkeys: FirewallRules, RestrictedServices, and Caché (if present). Do not delete the FirewallPolicy parent key itself, only the subkeys containing the rule definitions. This action removes the persistent binary data where the "lpacsensendr" rule is stuck.

    After clearing the registry keys, open an elevated Command Prompt and execute netsh advfirewall reset. This command will detect the missing registry structures and trigger the BFE to regenerate the factory-default policy store, effectively wiping the invisible block rules. Restart the machine immediately. Upon reboot, the Windows Firewall will be in its default state, and the Public profile should successfully permit DHCP negotiation and DNS resolution.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    VP

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.