[1031/181118.450:ERROR:registration_protocol_win.cc(103)] CreateFile: 系统找不到指定的文件。 (0x2)

[Waysma]

Issue Type: Bug

same bug as in gitignore bug (debug.log) #105161
#105161

happens again in 1.50.1

VS Code version: Code 1.50.1 (d2e414d, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	AMD Ryzen 5 3600 6-Core Processor (12 x 3600)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.95GB (27.66GB free)
Process Argv	--crash-reporter-id 6b4c2c37-414b-497e-a4ea-9b3ebff62a26
Screen Reader	no
VM	0%

Extensions (3)

Extension	Author (truncated)	Version
language-x86-64-assembly	13x	2.3.0
language-gas-x86	bas	0.0.2
cpptools	ms-	1.0.1

[weinand]

/needsMoreInfo

[weinand]

#105161 has been fixed in VS Code 1.49.

Please provide details of the issue you are seeing.

[Waysma]

#105161 has been fixed in VS Code 1.49.

Please provide details of the issue you are seeing.

it happens when I operate as follows(no exceptions):

1. click VScode via start menu for the first time;//nothing wrong
   then use the command "code -a ." to add some folder to the workspace
   

2. click VScode via start menu again to open another instance;
   then use the command "code -a ." to add a folder, it did add some thing, and gave the error message too
   

I updated from 1.42.1, which nothing wrong happens with the same operations

---

adding installing information on Nov 2nd: totally default installing with VSCodeSetup-x64-1.50.1.exe

[deepak1556]

The error message is from crash reporter initialization which you can ignore, is there any impact on vscode behavior due to this message, if not we can close this issue.

[Waysma]

hopefully be fixed in next release，anyway.

[CxRes]

I can report this is still occurring with 1.51.0 when using system setup and starting vscode with non-admin privileges. Please reopen!

[jordankkk]

debug.log still randomly created with vscode latest version (user installer), so far only happen on angular almost everytime open the vscode

[1111/084216.172:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

[songyang-dev]

I have a similar problem. This is inside the integrated terminal, on git Bash.

Song@LAPTOP-USBSGSDO MINGW64 ~/Documents/UDEM/ift6113/project/skinning_cor/Skinning with COR (master)      
$ code test.txt
[1128/195022.430:ERROR:registration_protocol_win.cc(103)] CreateFile: The system cannot find the file specified. (0x2)

[bytemain]

latest insiders version, also have this problem

A file named "debug.log" was generated in $(pwd)

[ruifortes]

I'm pretty sure this fix would take forever if it wasn't for Microsoft.... and the time was proportional to the available resources ;-)

[rob4226]

I have had this same issue for a while also. Inside every single directory of every single project a debug.log file gets created containing:

[1202/222752.856:ERROR:registration_protocol_win.cc(103)] CreateFile: The system cannot find the file specified. (0x2)
[1202/222753.192:ERROR:registration_protocol_win.cc(103)] CreateFile: The system cannot find the file specified. (0x2)
[1202/235330.481:ERROR:registration_protocol_win.cc(103)] CreateFile: The system cannot find the file specified. (0x2)
[1202/235334.513:ERROR:registration_protocol_win.cc(103)] CreateFile: The system cannot find the file specified. (0x2)

This same thing happened a few months back in a release but it was fixed...But now in the last release or two it is back and really annoying. Is there anyway to stop it? Thank you.

[deepak1556]

I unable to repro the situation where debug.log file is generated, have tried

• Latest stable both system and user install
• Latest insiders both system and user install

I was able to repro the log #109782 (comment) but that is harmless as I mentioned before.

Closing, can reopen if there is a repro for debug.log issue

[CxRes]

Just because you cannot reproduce this does not mean the bug has gone away! It just disregards what multiple users are reporting.

The problem in the first place is that message is so cryptic that no one except the one who wrote the code can know what it means. So how do you expect that ordinary users can provide a reproduction?

[deepak1556]

When we fixed #105191, we had removed the capability for our production builds to log to disk by default. After a while there was issue about debug.log files generated #108886, this turned out to be an issue with chrome https://bugs.chromium.org/p/chromium/issues/detail?id=1138853 . Although vscode fixed the first issue, the second issue has a way to leak into all electron apps based on chromium. We landed a fix in electron electron/electron#26250 to prevent this, but apps that have not picked up the fix would still be affected. So I am sure vscode is not the one generating the logs atleast on latest releases.

If it does, I would like a repro to investigate further for any meaningful solution. I am not closing the issue as no-fix, I just can't work on it without a repro. Thanks for your understanding.