Node-red suddenly doesn't start anymore after a BSOD

[difedef]

Hi marcus,

thanks for the reply. I actually solved the problem thanks to this post:

Windows 10 [error] Failed to start server: [error] TypeError: Cannot read property

Hi @dougcr4 this is a rare issue that we've never managed to get to the root cause of. If you are still hitting it, could I trouble you to add a bit of debug into the code to help us figure it out? Specifically, if you edit the file C:\Users\Dell\AppData\Roaming\npm\node_modules\node-red\node_modules@node-red\registry\lib\registry.js and look at line 186 you should see: set.types.forEach(function(t) { if (nodeTypeToId.hasOwnProperty(t)) { Please add the …

I deleted dependencies from the package.json and the package-lock.json of the incriminated flows appeared in the log and deleted the folder manually.

Now I have a warning though about git (I think it's beacuse I copied .node-red folder maybe?) causing this warning (it appears twice) in the debug section:

Error: fatal: detected dubious ownership in repository at 'C:/Users/xxx/.node-red/projects/ProjectName'
'C:/Users/xxx/.node-red/projects/ProjectName' is owned by:
	'S-1-5-21-16142359-3949692286-4010545788-1001'
but the current user is:
	'S-1-5-18'
To add an exception for this directory, call:

	git config --global --add safe.directory C:/Users/xxx/.node-red/projects/ProjectName

And now the git history disappeared.

Do I have to open a new topic about that?

P.S. the BSOD didn't related to node-red, but I think I used other softwares and VMs that caused the BSOD, without stopping my node-red service (and probably without deploying some changes)