New
#401
@EyeInTheSky
Thanks, I won't move to 2004 till I hear something positive and useful for me......
@EyeInTheSky
Thanks, I won't move to 2004 till I hear something positive and useful for me......
The thing that bothers me, is that Microsoft has always insisted on updating to the latest version and build number for security reasons. Holes that are patched to keep the bad guys out. Now, how is one suppose to update to the latest platform version if all it does is stop the computer from shutting down or booting up properly?
In other words, Microsoft is confusing customers with the "catch 22" that if you aren't updated to the latest and greatest, then you open yourself to vulnerabilities that are beyond their responsibility of maintaining a safe OS because one refuses to accept the latest and greatest.
Honestly, I think it is a scare mongering tactic used to push a product forcefully onto systems under the guise that you are not safe unless you update to the latest release. In other words, running 1909 and below, is a run at your own risk ideology pushed by Microsoft for security reasons. They can't lose with that approach and remain above reproach because ultimately it is the end users decision to choose whether or not their "catch 22" is convincing enough to push the user to submission because of doubt.
In light of it all, since everything has become "service-based" - the product sitting in front of you running a particular OS by Microsoft, has essentially become their property and realistically it has become a "hold your breath until the next boot" type scenario for many users.
I miss the days of owning the physical OS on Floppy or CD's because you could essentially pick that OS apart and run it the way you wanted; not how some company sees fit because advertising has become more important than the product quality itself.
Last edited by EyeInTheSky; 22 Jul 2020 at 13:06.
I'm getting event error 13 Vss error on shut down. Is it safe to not worry about this VSS error. I don't see anything not working on the computer. Everything seems alright. I'm on windows 20H2 and home version
I have been getting this errors since the upgrade to W10 1903. The past few months, even now in 20H2, this Events have become more and more rarer but they still take place. For example, I gotten them today and yesterday during shutdowns.
In my opinion, this Events are nothing to worry about. I dont even let them annoy me and expect them as something thats gonna happen sometimes. I suggest you ignore them and dont try fixing them. FWIW, even though I don't use System restore often, I tested it once to see if it still worked despite getting the Errors, and it does work properly. You can create System restore points manually. The only thing I noticed that doesn't work 100% as is supposed (and this is probably related to the errors) is that sometimes some points that the System wants to create automatically, fail, and a VSS error gets issued.
Bo
That's true but they bug my reboot. Why doesn't Microsoft fix their errors. They lag and lag and then another adds on like the BTHSB error or the 10016 error or the DNS error and so on and so forth. Ever since I have been on the XP beta it's always the same you have to create small tasks to circumvent these pesky little problems which they can fix a lot faster than we can.
Rant over, thanks and good night.
I've had this strange issue with VSS for a long time.
Today I completely uninstalled Macrium Reflect 8 (Home, registered) and they just stopped. Already rebooted 5 times and doesn't seem to happen anymore.
Macrium Reflect (or other backup programs) issue? Maybe MS changed something in the VSS system and these backup programs were never properly updated?
EDIT:
As always, after you tested something many times and say something is fixed, it happens again LOL
Ok, it seems a Window 10 problem indeed, still there.
- - - Updated - - - @EyeInTheSky
So... if I got it right, to fix it I have to set "COM+ Event System" service Log on: Local system account, correct?
Last edited by hexaae; 25 Jul 2022 at 04:50.
The solution by @Shanedh65 VSS Errors 8193 and 13
On page 28 is the solution. The bat file that you download and leaving it in Documents folder.
From then on I've never had these VSS Errors since. But I am on 1903 and remain on this version forever using Target Value! Pretty sure it should work for latest versions of Windows 10 as Microsoft doesn't seem to have bothered making a fix for this.
Or alternatively if you stop Cryptographic Service before shutdown/restart then the errors won't show.
Yes, I've read it, thank you (I don't even think you need to create the batch file: you can specify command + arguments directly: Program/script:%SYSTEMROOT%\system32\net
, arguments:stop cryptsvc
), but I'd prefer the EyeInTheSky alternative solution if there are no side effects... others can confirm it works?