Crock of shit would be a better description
Found my windows services using 95% of memory yesterday. Post total reboot virus scan showed nothing untoward. Best advice on the internet seems to be to randomly shut the services down until the problem seems to go away and then to permanently stop this particular service. But then we know MS will update the whole shebang in a weeks time and reenable it all whether you wanted, liked it or not.
The last update has totally bollxd one of my wifes machines, a 100euro trip to the shop (excluding her lost time etc etc etc) and the shop found nothing they could pin it on except questioning whether it was plugged direct into the wall or an extension cable (I mean, honestly... it was plugged in exactly the same as before the update and unless the power supply is really really really on a knife edge limit I cant see anything that should be triggering a succession of memory faults in different places, complaints about file handling and all manner of other random OS generated errors).
No roll back seems to be available (I thought during an update it was good practice to create a restore point you could go back to, MS dont do this and with no warning about when the OS is going to screw itself over you have no particular chance to).
The whole lot is written in C# leaving the whole mess is unpredictable, it is slow even when it hasnt memory leaked itself into a hole (something C# is supposed to help prevent), it is so flawed the updates come out faster than water from a tap, MS should realise the whole thing is a bad idea and give everyone lessons on linux and provide all users with a free linux package... finally destroying the 'product' that is inflicting misery on millions.
When I worked for them they actually tested stuff before shipping it, made sure it was used internally and would not release it with showstopper defects like 'it doesnt bloody start quicker than I can make a cup of tea' or 'I have grown old and died while waiting for the volume slider to appear'.