" Did you make a batch file for it then? "...............would be very usefull , we could make a task with it also ; stop Cryptographic service , at reboot/shutdown. ( Task Scheduler ! )
Then this will happen automaticly and we dont see these VSS-errors never again................awsome !!
Here is the batch file that I created to stop the cryptographic service. You need to run this bat file as an administrator, then you can shutdown or reboot windows.
You must use this batch file before shutting down. I know it works for me.
If you have windows 10 pro you can use gpedit to run this bat file everytime you shutdown or restart windows by going to gpedit - computer configuration - windows settings - scripts - shutdown. Select add, select the bat file then ok. You don't need to run this batch file if you use this option.
" I know it works for me. "...............hmmmm..............seems to work here too !!
Made a new install and applied your solution ......still no VSS-errors in sight , have to test a few days more , but it looks like your solution is THE solution , which really does the job !!
Dont know how to thank you , have been working on this problem for a few weeks now .
If I can do anything to show my appreciation , let me know , please ! THANKS A LOT !!
No problem, a little bit of looking at the event logs and research. It seems to work, hopefully it sticks.
Ok. I have been trying to hunt this down and I read the dberr.txt that I found in the catroot 2 folder. Towards the end of the installation it has 4 errors that have to do with the database. The errors are...
CatalogDB: 8:07:21 AM 6/17/2019: catdbsvc.cpp at line #1245 encountered JET error -1601
CatalogDB: 8:07:21 AM 6/17/2019: catdbsvc.cpp at line #1245 encountered JET error -1601
CatalogDB: 8:07:21 AM 6/17/2019: catdbsvc.cpp at line #1245 encountered JET error -1601
Now looking for this error and also 2 esent errors during setup event id 636 and 640 under warnings and of course our errors it points to a corrupt database in the catroot2 folders. Has to do with cryptographic services and windows update components. They seem to be interconnected and ese disk flush also seems to be connected with all this mess. I have been searching on technet and other forums for the answer. The answer seems to be a consensus in all that I have read to fix the catroot2 and software distribution folder. I have not tried this yet and want to know what you think. So what I think is there is corruption in the database and what cause the vss13 and 8193 errors is it couldn't write the restore image due to the corruption. I have only seen the errors right after reboot on repair install and so far not again. I did repair the indexer by rebuilding but am unsure if that worked to stop the errors. Anyway here is the post . Tell me what you think.
I did a search for the 1601 error in the text file and everything is pointing to this.
https://answers.microsoft.com/en-us/...5-31acc430bd08
Will do some study , for now , Im very pleased with the "stop service"- batfile , placed ( hidden file) in C: , made a gpedit-shutdown-task with it and , untill now (!) , still a clean eventlog ............
No other "fixes" or "tricks" , just this little batfile makes it all-right............
Yes, until I know for sure that catroot2 is what is causing these errors I won't do anything yet. If I see them again I may attempt the fix for catroot2. I have been seriously considering a format and clean install and may do that at some point before the next big upgrade. For now I am not using the script file. Since I have not seen the error again I will just keep my eyes open.
" a format and clean install "..............wont help us , waste of time !
I know , for sure , its a 1903-bug , so clean install is not the way .
Will use the " bat-file solution " , which still works fine , untill MS wakes up and will fix it ..........
btw ; will see if this latest fix will be really "solid " ...........keep in touch with you , will report if something might change.........
Power shell command
Get-Service cryptsvc | Stop-Service -PassThru | Set-Service -StartupType disabled.
I will see if that is the fix on my machine.
Quote