New
#31
Well, I am not an expert by any means, but I believe MS finally fixed the issue caused by 2 GiB memory machines in a recent update (Can't remember where I read about it at this point in time). However, from what I understood, the issue (Which seemed to come out with a windows update 'update', in spring-ish of this year) mostly only affected machines with less than 4 GiB of RAM, which is why I simply decided to upgrade my RAM to 4 GiB to avoid the issue (For only $8.99 on ebay, it was an easy and painless fix).
I originally used that code above as a temporary fix. Once I did some research in my free time, and felt confident more RAM would fix the issue, as it seemed MS was not doing anything quickly to address it, I ordered the memory to alleviate the problem. It seems however that very recently MS did finally release a KB fix for the issue, but the increase in RAM never hurts.
My only issue was is it seemed that code left a residual effect of changing the WSCSVC from it's default setting to manual even after I removed it (or rather, it probably changed it when run originally, and removing it did not change it back). I did not change the service(s) (well... the code I copied and ran did, but I did not knowingly stop the service(s)).
Since the computer now has all action center and windows update services running normally upon reboot again and my memory usage is holding @ ~25% (of 4 GiB), I think my problem is resolved and I will skip the long winded difficult fix I do not seem to need!
Thanks!