![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Windows jollies... (not!)
Sep. 24th, 2013 10:41 pmWindows appears to have gone back to randomly refusing to open files that are double-clicked or highlighted and selected using the 'Enter' key. When this happens, Task Manager won't start, Windows Explorer sometimes kicks the bitbucket, and the machine will neither restart or shut down.
I've tried running sfc /scannow, which informs me of a number of corrupt files, and I'm running dism, but it's failing with a 3017 error.
I'm counting on the fact that I can't seem to find any groundswell of users with similar problems to conclude that the problem (which had manifested itself on my Acer Windows 7 machine as well) may be connected with one or more programs that are running on my specific machine, i.e., due to my setup than to anything necessarily wrong with Windows. Thanks to the promiscuous installation and launch of miscellaneous crap programs by almost every application out there, however, it's not going to be easy to track this problem down.
There is supposedly a way to restore one's Windows 8 machine without losing data, but there's a twist: you may not lose data, but all non-Windows executables are apparently uninstalled in the process. One's only consolation is that a file containing a list of uninstalled programs is left behind on the desktop. Brrr. That sounds like a pretty radical step, to me (although I can envision situations where it might come in handy).
But... (particularly in light of the news in the postscript) let's hope it doesn't come to that. On the other hand, let's also hope I don't have to reboot my work machine half a dozen times a day, either. That reminds me too much of various periods during my past history with Windows.
* * * In other news, after my trip to Kazakhstan, my hospital visit, and my recent adventures in Colorado, I made sure tonight was my "return to tai chi" night. I was certainly rusty in the push-hands department, but managed to get through the warmup and the form without a problem, and through the lesson as a whole without tiring myself out. In fact, to tell you the truth, I actually felt pretty good afterward.
Cheers...
P.S. UPDATE of 10:43 pm: I had restarted my machine (to back out of previous changes made by dism) and was running the program again while tapping out this post (the command line was: dism /online /cleanup-image /restorehealth) and shortly after posting, the program's text-based progress graphic jumped to 40%, then 80%, and finally 100% completion and announced that "component store corruption was repaired." Being the impatient type that I sometimes am, I am rerunning sfc /scannow to see what it may have to say in the matter. I am cautiously hopeful.
I've tried running sfc /scannow, which informs me of a number of corrupt files, and I'm running dism, but it's failing with a 3017 error.
I'm counting on the fact that I can't seem to find any groundswell of users with similar problems to conclude that the problem (which had manifested itself on my Acer Windows 7 machine as well) may be connected with one or more programs that are running on my specific machine, i.e., due to my setup than to anything necessarily wrong with Windows. Thanks to the promiscuous installation and launch of miscellaneous crap programs by almost every application out there, however, it's not going to be easy to track this problem down.
There is supposedly a way to restore one's Windows 8 machine without losing data, but there's a twist: you may not lose data, but all non-Windows executables are apparently uninstalled in the process. One's only consolation is that a file containing a list of uninstalled programs is left behind on the desktop. Brrr. That sounds like a pretty radical step, to me (although I can envision situations where it might come in handy).
But... (particularly in light of the news in the postscript) let's hope it doesn't come to that. On the other hand, let's also hope I don't have to reboot my work machine half a dozen times a day, either. That reminds me too much of various periods during my past history with Windows.
Cheers...
P.S. UPDATE of 10:43 pm: I had restarted my machine (to back out of previous changes made by dism) and was running the program again while tapping out this post (the command line was: dism /online /cleanup-image /restorehealth) and shortly after posting, the program's text-based progress graphic jumped to 40%, then 80%, and finally 100% completion and announced that "component store corruption was repaired." Being the impatient type that I sometimes am, I am rerunning sfc /scannow to see what it may have to say in the matter. I am cautiously hopeful.
