Windows 10: Query on which computer seems at fault with network error

I have just installed 2 PCs fresh with Windows 10. One of them can connect to the other fine to share files. My other PC can see the other one, but can't access any files from the shared folders on that PC.

So which computer is likely to be the fault ? The one that can't connect to the PC that gives the error, or the PC that can't be connected to ? I ask because I am going to uninstall network adapters but want to try that on the PC at fault. As mentioned, one of my PC's can connect to the other one fine.

I uninstalled Comodo firewall but still got the problem. I have disabled Windows Firewall. Error message is : Windows cannot access \\AMD-PC 0x80070035 The network path was not found.

Thanks all.

:)

 

Stopping PC Suite Loading

Sometimes,(not very often) when closing several applications (it does not seem to matter which), the computer hangs for a second and then the MS error reporting menu pops up, the return reply from microsoft states that there is a known problem (does not
say what) with PC Suite and that Nokia are aware of it. It suggests contacting Nokia.

I think this is the fault - I got the info from the log.

15/02/2006 14:49 Application Error Faulting application datalayer.exe.

 

Windows 10 dwm.exe errors

I am getting several dwm.exe errors during the course of the day. The computer does not crash or blue screen, I just see this error logged usually once or twice daily. This all seemed to start happening after the November update. I have run check disk, sfc
/scannow, and check health command, all of which come back with no errors.

So should I be worried about this and is there a fix?? Thanks!!

Faulting application name: dwm.exe, version: 10.0.10586.0, time stamp: 0x5632d756

Faulting module name: combase.dll, version: 10.0.10586.0, time stamp: 0x5632d3ca

Exception code: 0xc0000005

Fault offset: 0x0000000000067e5c

Faulting process id: 0x1874

Faulting application start time: 0x01d12d98bf1dbbaf

Faulting application path: C:\WINDOWS\System32\dwm.exe

Faulting module path: C:\WINDOWS\system32\combase.dll

Report Id: 062699e7-8a77-44fa-8224-3d00f8e675e2

Faulting package full name:

Faulting package-relative application ID:

 

Hi BlizzardUK

One PC lets call it "A" can see the other PC, called "B", and can actually see the files on "B".

Now "B" on the other hand can see "A" but can't actually see the files on "A".

I would go to PC "A" and ensure the files are marked as Shareable.

You didn't mention what you are using for sharing like Homegroup, etc.

 

Hi. Yes, my AMD PC, which I simply labelled AMD-PC (let's call PC "A") can indeed see my INTEL-PC (call PC "B") and also access files on it. However PC "B" cannot access PC "A" at all, and all shares show up as white blocks on Homegroup. This error is both via HomeGroup and normal Network.

However, the folder I have shared on PC "A" called Transfers, will show up as a white icon on PC "B" and this will vanish if I unshare it on PC "A", so this must mean there is some kind of link there as instantly it will vanish being visible on PC "B" when unshared.

Any ideas ? Thanks.

 

There is an issue with shares that has been threaded to death but I don't think anyone has found the ideal solution. It is all related to which PC becomes the Master Browser.

One thing you could try is resetting network on "A". Simple process.

Start => Settings => Network and Internet => scroll to bottom of righthand side => click reset network. This causes Windows to "Forget" all wireless passwords.

Back to Master Browser. You will see some threads, like this one, that suggest using a USB key in router and allowing Router to become master browser. Then power up other devices.

Creators Update destroyed Network Discovery on wired LAN

Also seems to work well if you have a 1607 computer that you power up first. You can read thread. Not sure if this is the same issue you are having.

I would also try this with both PC's on Clean Boot just to make sure third party firewalls are not involved.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts


Ken

 

Thanks for your advice. I tried everything, including upgrading with ISO over the top of existing version and the network resetting and uninstalling. The only thing that worked was a total Windows 10 reset with complete removal of files. I have no idea why. Big shame as I have to reinstall everything, but it now works at least.

Thanks.

 

Great.

MS has to assign a team to this issue. Sure sharing works for a lot of users but there is a very large group of users that Sharing is not working for.

Thanks for sharing your solution.