How to Fix Network Sharing Issues Between Windows 10, 11 PCs (2025 Guide)

How to Fix: One-Way or Broken Network Sharing Between Two Windows PCs (Windows 10 & 11)


 Quick Fix (For Experienced Users)

If PC-A can access PC-B, but PC-B cannot access PC-A:

  1. Set both PCs to “Private Network”
  2. Disable password-protected sharing on both
  3. Enable these Windows services:
    • Function Discovery Provider Host
    • Function Discovery Resource Publication
  4. Access shared folders using \PC-NAME instead of \192.168.x.x
  5. Share a folder with “Everyone” Read/Write
  6. Optional: Enable SMB 1.0 for legacy testing
  7. Optional: Allow insecure guest logon via Group Policy

Are You Facing This?

You’re probably here because:

  • You can access one PC, but the other one fails to connect
  • Ping works but file sharing fails
  • You get “Network path not found” or “0x80070035” errors
  • You’re stuck at the “Enter Network Credentials” prompt
  • Your PCs don’t appear in the network anymore

Step-by-Step Fix (For Beginners)

Step 1 – Set Network to Private

  • Settings > Network & Internet > Wi-Fi/Ethernet > Your Network
  • Select: Private Network (on both PCs)

Step 2 – Adjust Sharing Settings

  • Control Panel > Network and Sharing Center > Advanced sharing settings
  • Turn ON:
    • Network discovery
    • File and printer sharing
  • Turn OFF:
    • Password protected sharing
  • Save changes

Step 3 – Start Required Services

  • Win + R > type services.msc
  • Set these to Automatic and Running:
    • Function Discovery Provider Host
    • Function Discovery Resource Publication

Step 4 – Share a Folder

  • Right-click folder > Properties > Sharing tab > Advanced Sharing
  • Check “Share this folder”
  • Permissions > Add “Everyone” > Allow Read/Write
  • Confirm via Security tab: add “Everyone” with same access

Step 5 – Access from Other PC

  • In File Explorer: \\PC-NAME\SharedFolder
  • If it fails, try: \\[IP Address]\SharedFolder
  • Use matching username/password when prompted

Step 6 – Optional: Enable SMB 1.0 (Testing Only)

  • Control Panel > Programs > Turn Windows Features On/Off
  • Enable “SMB 1.0/CIFS File Sharing Support”
  • Reboot
  • Only use temporarily for compatibility tests

Step 7 – Optional: Guest Logon Fix (Pro Only)

  • Win + R > gpedit.msc
  • Go to:
    • Computer Config > Admin Templates > Network > Lanman Workstation
    • Enable “Insecure guest logons”

Common Errors Explained

  • 0x80070035 – Network path not found
  • 0x80004005 – General access denied (permissions)
  • “Extended error occurred” – Wrong credentials or services not running
  • Login prompt keeps showing – Try matching local accounts/passwords

Extra Troubleshooting Tips

  • Restart both PCs after changes
  • Try different account with a password
  • Temporarily disable firewall/security software
  • Restart router
  • Ensure same subnet (e.g. 192.168.1.xxx)
  • Avoid using IP, prefer \PC-NAME

🚡 Security Advice

  • Don’t leave shared folders open forever
  • Always create a dedicated user with a password
  • Avoid SMB 1.0 for daily use – it’s insecure

Frequently Asked Questions & Expert Additions


Why does one PC see the other, but not vice versa?
This is usually caused by Windows disabling certain discovery services by default. Make sure both “Function Discovery Provider Host” and “Function Discovery Resource Publication” services are running on both machines. Also verify you’re on a Private Network.

Why am I stuck at the login prompt even with correct credentials?

  • You might be using the wrong format. Try entering the PC name before the username like: PCNAME\username

  • Make sure the password is not blank — Windows blocks blank passwords over networks by default.

  • Try using a local account with matching credentials on both machines.

What’s the difference between using IP vs. PC name?

Using \PC-NAME\SharedFolder is more reliable across reboots and router restarts, because IP addresses can change unless you set up DHCP reservation in your router.

Is SMB 1.0 safe to use?

No. SMB 1.0 is outdated and vulnerable. Only enable it temporarily for compatibility testing with older devices, and turn it off again afterward.

Should I use guest access?

Only if you understand the risks. Guest access can bypass authentication and is often blocked by default in Windows 10/11 Pro. It can be enabled via Group Policy but is not recommended unless necessary for legacy devices.

What causes the 0x80070035 error?

This typically means the path was not found. Causes:

  • Typo in share name or PC name

  • Firewall blocking file sharing

  • Network profile set to Public

  • Required services are not running

Why do shared drives disappear after reboot?

  • Windows sometimes “forgets” mapped drives unless you enable “Reconnect at sign-in”

  • Mapped drives based on dynamic IPs can break when IP changes — use PC name instead

What does “Account restrictions” mean in error messages?

  • You may have tried to connect using an account without a password

  • The account may have login hour restrictions

  • A policy might block network logins (check Local Security Policy)


Pro Tips from Real Users (Based on Forum Insights)

  • Use the full share name instead of IP address — many reported sudden success just by switching to \ComputerName\SharedFolder

  • Rebooting both PCs after a change is often necessary — especially after changing services or credentials

  • Use identical user accounts on both PCs for easiest access (same name + same password)

  • Prevent automatic updates temporarily if you have an older device with working shares — new builds may reset settings

  • Use gpedit.msc to disable digital sign requirements under:

    • Local Policies > Security Options > Microsoft Network Client: Digitally sign communications (always)

    • Set to Disabled

Bonus Fixes (When Everything Else Fails)

  1. Delete mapped drives and recreate them using correct share name

  2. Check firewall settings — allow File and Printer Sharing on Private networks

  3. Add these registry keys if still stuck (be careful):

    • HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

    • Set AllowInsecureGuestAuth to 1

  4. Set static IPs for both PCs (only if confident)

  5. Create a batch script to remap drives at startup


Summary
Fixing Windows file sharing issues requires careful setup of:

  • Network type

  • Services

  • Credentials

  • Permissions

Using PC names, disabling password protection (carefully), and verifying services go a long way. Adding FAQ content helps boost your troubleshooting and your blog SEO.

Let us know in the comments if a specific trick worked for you!

Fix VEGAS Pro Crash When Importing MTS Files with AC3 Audio on Windows 11

If VEGAS Pro crashes every time you import an .MTS file with AC3 (Dolby Digital) audio, especially from Sony cameras like the SLT-A58, you’re not alone. This is caused by the removal of native AC3 codec support in newer Windows builds. Here’s how to solve it — for good.


The Error

When importing .MTS clips:

  • VEGAS crashes immediately
  • Error: Unmanaged Exception (0xe06d7363)
  • Fault Module: KERNELBASE.dll

These .MTS files usually contain:

  • Video: AVC (H.264) 1920x1080i, 25fps
  • Audio: AC-3, 256 kbps, stereo, 48.0 kHz (Dolby Digital)

The Fix (with images)

Step 1: Download and Install AnWave

Get the codec fix tool here:
Download AnWave v6.10.17.26

Run the installer:

AnWave Installer

Click Install and proceed.


Step 2: Launch AnWave.exe

Navigate to the folder:
C:\Users\YOURNAME\Desktop\AnWave-2024-6.10.17.26-Windows-x64\

Double-click AnWave.exe


Step 3: Enable Dolby Digital Atmos Support

In the AnWave app:

  • Go to the System tab
  • Scroll down and click Microsoft Dolby Digital Atmos Pack
System Tab
Dolby Digital Atmos

This will install Dolby audio support back into your Windows system.


Final Step: Reboot and Test in VEGAS

  • Restart your PC
  • Open VEGAS Pro
  • Import your MTS file — no crash, audio works!

Bonus Tip

Want to preview MTS files in Windows 11 directly?
How to open MTS files in Windows 11


Conclusion:
AC3 support is essential for editing older MTS files. AnWave and Dolby Atmos restore this capability without the need for risky codec packs. Worked perfectly for my Sony SLT-A58 footage in VEGAS Pro 21.


Let me know if you want a WordPress export version buddy, or if I should embed your YouTube link once ready!

Final Step: Test in VEGAS

  • Launch VEGAS Pro
  • Import your MTS file — it should already work without a reboot
  • If it still crashes, reboot your PC and try again

Sure buddy, here’s a “Frequently Asked Questions” section you can add below your blog to boost SEO and traffic:


Frequently Asked Questions (FAQ)

Why does VEGAS Pro crash when importing MTS files?
VEGAS Pro often crashes when importing .MTS files that contain AC3 (Dolby Digital) audio, especially on Windows 11 systems missing the AC3 codec.

How do I fix AC3 audio issues in VEGAS Pro?
Install the AC3 codec using the AnWave tool and enable Dolby support. This solves most import and playback issues.

Can I open MTS files in Windows 11 without converting them?
Yes, but you’ll need proper codec support. See this guide: https://izzylaif.com/en/how-to-open-mts-files-in-windows-11

Is AnWave safe to use for AC3 codec installation?
Yes, it’s an open-source utility trusted by many users to restore missing codec functionality in modern Windows builds.

Does this fix apply to other Sony cameras like A57 or A77?
Yes, if your camera records in .MTS with AC3 audio, the same fix should work.

Sure buddy, here’s an extra section for under je blog met zoektermen en issues waar mensen op googelen:


Common Search Phrases That Lead Here

If you searched for any of these, you’re in the right place:

  • “VEGAS Pro crashes when importing MTS file”
  • “MTS file crashes VEGAS Pro 21”
  • “How to fix AC3 audio crash in VEGAS Pro”
  • “Windows 11 MTS import problem VEGAS”
  • “VEGAS Pro KERNELBASE.dll error”
  • “Sony SLT-A58 MTS not working in VEGAS”
  • “Unmanaged Exception 0xe06d7363 VEGAS fix”
  • “VEGAS can’t open MTS with Dolby audio”
  • “Fix .MTS import error in VEGAS Pro”
  • “Missing AC3 codec Windows 11 VEGAS crash”

These are the issues that this blog post solves.