question

Slion avatar image
0 Votes"
Slion asked DylanZhu-MSFT edited

Network Kernel Debugging setup fails

Has anyone been able to provision the target computer as explained there:
https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1

It did create a user account on the target computer which looked very promising but then fails saying:
"Error message: Unable to create directory: C:\DriverTest\Setup"

Follows a bunch of other errors which I'm assuming are all related to the fact that it fails to copy files to the target computer.

I'm running both computers on a workgroup as opposed to a domain.

vs-debugging
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DylanZhu-MSFT avatar image
1 Vote"
DylanZhu-MSFT answered DylanZhu-MSFT edited

Hi Slion,

Note sure if there are some steps missed. You can confirm if permission of the directory has been modified to the Authenticated Users group. And you can try to re-confirm the steps about firewall:

  1. On the target computer, in Control Panel, go to Network and Internet > Network Sharing Center. Note your active network. This will be Public network, Private network, or Domain.

  2. On the target computer, in Control Panel, go to System and Security > Windows Firewall > Advanced settings > Inbound Rules.

  3. In the list of inbound rules, find all Network Discovery rules for your active network. (For example, find all Network Discovery rules that have a Profile of Private.)Double click each rule and open the Scope tab. Under Remote IP address, select Any IP address.

  4. In the list of inbound rules, locate all File and Printer Sharing rules for your active network. For each of those rules, double click the rule, and open the Scope tab. Under Remote IP address, select Any IP address.

Update:
You can have a try this workaround:
As Administrator, run Developer Command Prompt for VS 2019
Run the following commands in the VS Developer Command Prompt:
cd /d %VCToolsRedistDir%\debug_nonredist
MKLINK /J x86\Microsoft.VC141.DebugCRT x86\Microsoft.VC142.DebugCRT
MKLINK /J x64\Microsoft.VC141.DebugCRT x64\Microsoft.VC142.DebugCRT

If it doesn't work, we suggest to report it to product team: https://developercommunity.visualstudio.com/report?space=8&entry=problem

Best Regards,
Dylan


If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Slion avatar image
0 Votes"
Slion answered DylanZhu-MSFT commented

Hi Dylan, thanks for helping.
I just double check all of that after having done it already yesterday. Everything was setup as it should.
For good measure I added Full Control to the folder permissions but that did not help either.
Here is again the first error from the logs:

An error occurred on the target machine while copying a file from the host machine.
Error code: 0
Error message: Unable to create directory: C:\DriverTest\Setup.
Progress event: Current: 1, Max: 15, Message: " Task "Copying required files" was aborted because an error occured on the target machine during execution.

BTW that folder was already created on the target machine by some MSI that's part of the configuration process.
What it shows though is that it does not have access to the target file system basically.

I've also enabled C$ access to the target computer but that did not help either. I can create file in that folder myself from the host computer but the provision process fails to do that for some reason.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Slion , thanks for feedback. You can have a try this workaround from this thread:
As Administrator, run Developer Command Prompt for VS 2019
Run the following commands in the VS Developer Command Prompt:
cd /d %VCToolsRedistDir%\debug_nonredist
MKLINK /J x86\Microsoft.VC141.DebugCRT x86\Microsoft.VC142.DebugCRT
MKLINK /J x64\Microsoft.VC141.DebugCRT x64\Microsoft.VC142.DebugCRT

If it doesn't work, we suggest to report it to product team: https://developercommunity.visualstudio.com/report?space=8&entry=problem

1 Vote 1 ·