Issues with Windows 11 24H2 Affect Internet Connectivity, Wi-Fi Stability, and Network Sharing, Resulting in More BSODs

Key Notes

  • BSOD problems identified with Intel Z890 motherboards.
  • Network connectivity challenges due to DHCP issues.
  • Practical solutions available for major update issues.

Navigating Challenges with Windows 11 24H2 Update

The recent Windows 11 24H2 update has sparked various performance-related issues across several hardware configurations, specifically concerning BSODs and connectivity challenges. Understanding these problems and their solutions is crucial for users affected by this version update.

Understanding BSOD Challenges

Users with Intel Z890 motherboards have reported instance of the Blue Screen of Death (BSOD), particularly with the Core Ultra 200S series. This issue primarily arises from graphical compatibility conflicts.

Step 1: Implementing the BSOD Fix

If you experience a BSOD, follow the steps below:

  1. Restart your computer and access the BIOS by pressing Del or F2.
  2. Navigate to the “Advanced” section and find “Internal Graphics.”
  3. Change the setting to “Disabled, ” and confirm with F10.
  4. Reboot your system to effectively switch to GPU output.

Pro Tip: Check your motherboard manufacturer’s website for the latest BIOS updates for better compatibility.

Network Connectivity Challenges

Many users have reported that after the update, devices often receive a 169 IP address, indicating no connection to the network, primarily caused by DHCP issues.

In various instances, updating the network drivers or resetting settings did not resolve the problem. However, setting a static IP has proven helpful for some users.

Step 2: Resolve Invalid IP Address Issues

To fix IP address distribution, consider the following suggestions:

  • Ensure DHCP is functioning correctly in your network configuration.
  • Manually assign a static IP to see if it resolves the connection issue.
  • Inspect your network adapter settings to ensure they match the functionalities you require.

Resolving Internet and Wi-Fi Connectivity Problems

To address your connection issues, you can try the following:

Solution 1: Adjust Service Dependency in the Registry

  1. Launch the Registry Editor as an administrator.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WcmSvc.
  3. Locate the DependOnService entry and remove WinHTTPAutoProxySvc.
  4. Leave only RpcSs and NSI.
  5. Save changes and restart your computer.

Solution 2: Enable WinHTTP AutoProxy Service

  1. Open the Registry Editor with administrative privileges.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinHttpAutoProxySvc.
  3. Change the Start entry from 4 (disabled) to 3 (manual).
  4. Save and reboot your system.

Solution 3: Adjust Windows Connection Manager Service

  1. Open the Command Prompt as an administrator.
  2. Enter the command sc config wcmsvc depend= RpcSs/NSI and press Enter.
  3. Reboot your PC for changes to take effect.

Preventing Sharing Issues

Another concern involves computers not being visible on the network, affecting file and printer sharing capabilities. This may be linked to the Function Discovery Resource Publication service.

Adjusting its startup type from “Manual (Trigger Start)” to “Automatic” may help resolve sharing visibility issues.

Conclusion

With a host of connectivity and performance problems arising post-Windows 11 24H2 update, users have various solutions at their disposal to tackle these issues effectively. For those severely affected, reverting to the previous version might be the best interim solution.

Conclusion

FAQ (Frequently Asked Questions)

What are the main issues with the Windows 11 24H2 update?

Users are reporting BSOD issues, poor network connectivity, and problems with Adobe applications’ performance.

How can I resolve BSOD issues related to the update?

Disabling internal graphics in the BIOS and ensuring the latest BIOS version is installed can mitigate BSOD occurrences.

Can I fix network connectivity issues?

Yes, you can try assigning a static IP address or adjusting service dependencies through the Windows Registry.