Windows 10: Two error NetBT ID 4300

Hello,

I dual-boot system with Windows 7, Windows 10 Pro (default).

After the latest updates to v.1607 me I have this problem, if you boot the system, I access directly to Windows 7 and shut the system normally, no longer go into Windows 10 pro on the same day.

List all events to make + understandable.

Events in the registry of Windows 10 pro, which I think are created during the boot screen, waiting for access to Windows 7:

Starting the system: (Windows registry 10 pro bed the next day)

-system started operating the system time 2016-08 - 29T18: 36: 31.495010400Z.
-Last Been successful arrest: true. Last startup was successful: true. 08.29.2016 20:36:31
Startup -type: 0x0. 08.29.2016 20:36:31
-criteria The Start menu: 0x1. 08.29.2016 20:36:31
-In The system there are 0x2 boot options. 08.29.2016 20:36:31
-The Bootmgr file has been waiting for user input for 0 minutes. 08.29.2016 20:36:31
-Loading The file system 'FileInfo' (10.0 Filter, 2016-07 - 16T03: 42: 32.000000000Z) and recording
Filter Manager failed. 08.29.2016 20:36:32
-Loading The file system 'Wof' (10.0 Filter, 2016-08 - 06T05: 45: 14.000000000Z) and recording Management
managed filters. 08.29.2016 20:36:32
-Loading The file system 'WdFilter' (10.0 Filter, 2016-07 - 16T03: 38: 51.000000000Z) and recording
Filter Manager failed. 08.29.2016 20:36:32
-Volume C: (\ Device \ HarddiskVolume2) is intact. You do not need to do anything. 08.29.2016 20:36:35
-Volume F: (\ Device \ HarddiskVolume3) is intact. You do not need to do anything. 08.29.2016 20:36:36
-Volume E: (\ Device \ HarddiskVolume6) is intact. You do not need to do anything. 08.29.2016 20:36:36
- Load the file system 'FileCrypt' (10.0 Filter, 2016-07 - 16T03: 35: 59.000000000Z) and recording
Filter Manager failed. 08.29.2016 20:36:37
-Loading The file system 'npsvctrig' (10.0 Filter, 2016-07 - 16T03: 44: 29.000000000Z) and recording
Filter Manager failed. 08.29.2016 20:36:37
-State Standby connectivity: Disconnected, reason: NIC Compliance 29/08/2016 20:36:37
-The Processor 0 0 Group exposes power management capabilities include:
Type been idle: Idle States ACPI (C) (1 state / s) 29/08/2016 20:36:43
-The First group 0 processor exposes power management capabilities include:
Type been idle: Idle States ACPI (C) (1 state / s) 29/08/2016 20:36:43
-Volume Q: (\ Device \ HarddiskVolume4) is intact. You do not need to do anything. 08.29.2016 20:36:45
-Volume \\? \ Volume {f5d93205-0000-0000-0030-000000000000} (\ Device \ HarddiskVolume1) is intact.
You do not need to do anything. 08.29.2016 20:36:46
-Volume H: (\ Device \ HarddiskVolume5) is intact. You do not need to do anything. 08.29.2016 20:36:46
Stop -Transition initiated by the kernel power manager.
Reason for: kernel API 08/29/2016 20:36:52
2 Errors: NetBT ID 4300
Log Name: System
Source: NetBT
Date: 29/08/2016 20:36:55
Event ID: 4300
Task Category: None
Level: Error
Keywords: Classic
User: N / A
Computer: PC-Piero
Description:
Unable to create the driver.
XML Event:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name = "NBT" />
<EventID Qualifiers = "49152"> 4300 </ EventID>
<Level> 2 </ Level>
<Task> 0 </ Task>
<Keywords> 0x80000000000000 </ Keywords>
<TimeCreated SYSTEMTIME = "2016-08-29T18: 36: 55.265194800Z" />
<EventRecordID> 12392 </ EventRecordID>
<Channel> System </ channel>
<Computer> PC-Piero </ Computers>
<Security />
</ System>
<EventData>
<Date>
</ Date>
<Binary> 000000000100320000000000CC1000C014010000890100C000000000000000000000000000000000 </ Binary>
</ EventData>
</ Event>
-system stopped operating the system time 2016-08 - 29T18: 36: 56.329223000Z.

Windows 7 registry:
operating system started at the time of system 2016-08-29T18: 37: 10.375199800Z.
The two systems do not have the same name; 7 has Xxxxx-PC and 10 has PC-Xxxxx

Is there a solution?
Thank you

:)

 

BITS start failure - clean install of Windows 10 Pro

Phil

Log Name: System

Source: Microsoft-Windows-WindowsUpdateClient

Date: 12/01/2017 03:52:14

Event ID: 19

Level: Information

Description:

Installation Successful: Windows successfully installed the following update: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3213986)

This is the latest update! If Bits was continually failing this update would not have installed.

Log Name: System

Source: NetBT

Date: 14/01/2017 17:58:54

Event ID: 4321

Level: Error

Description:

The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.2.183. The computer with the IP address 192.168.2.1 did not allow the name to be claimed by this computer.

This is a repeating error.

Event ID: 4321 Source: NetBT

 

Odd behavior since aniversary update

I don't have a one drive account. I don't trust cloud services.

Edit about most recent occurance of glitch: I've looked through every single log in the event viewer and not one of them registered anything at the time of the glitch, or shortly after. The closest thing I could find was 3 minutes before the glitch and that
was identified as a NetBT error (event id: 4307).

 

Is there a solution?
Thank you[/QUOTE]

Yes, when you boot into W 10, when restarting for whatever reason do not switch OS's. If you boot to W 10 and you wish to restart, restart always to W 10 and when you are done, shutdown W 10. Same for W 7. After a shutdown, boot again to any OS you like. Also, when you see the Boot Manager screen, if you boot to W 10 let it run automatically, after 30 seconds. If you want to boot to W 7 monitor the HDD led light and when it finishes flashing, click on W 7 icon to enter W 7 OS. Usually, it takes 15-20 secs for the led light to finish flashing. If you do it before, and while Boot manager still loads, you will get such NetBT events, they are usually harmless but if you want not to see such events in Event Viewer, follow each time the procedure described above. I'm doing the same each time, and never had NetBT events.
I'm also assuming that you have Fast Startup disabled under W 10 but if you don't please disable it.

Cheers,

 

Probably you're right, a full explanation, which no one was able to give, and that I had guessed, but I could not explain ...
Thank you.