![]() ![]() I hear Windows.old gets periodically and automatically deleted. ![]() Windows upgrades apparently touch user directories. the right Users\User\AppData was in what I moved into C:\Windows.bad, but documents and desktop icons were in Windows.old. Rolling back to the previous version failed with no error message more descriptive than “it didn’t work.” Moving C:\Program Files, C:\ProgramData, C:\Users, C:\Windows (etc.) into C:\Windows.bad, and moving C:\Windows.old\* into C:\ got me a somewhat usable system, but some things still got moved to the new system from the old system, so I’ve been cherry picking things from C:\Windows.bad to move back, i.e. ![]() One of our customers had this happen to their laptop. But I think they will be needed until either I or Windows 10 expires. I shouldn’t need heather dangling from my USB stick and a rabbit’s-foot and horseshoe stuck on my case in order to encourage my ‘puter to work, either. As will negotiating the stressful minefield of working out (thank goodness for Woody and contributors, by the way) which patches to install, when to install them or indeed, when to rip them back out. The dizzying game of patching the patch to repair the patch or rolling back to versions of Win 10 that themselves still require patching will continue ad-infinitum. ![]() But of course such a frantic ‘delivery timescale’ means non-Microsoft software isn’t the only thing guaranteed to break, is it? It means that each new Win 10 version itself is also guaranteed to be broken on release. Not for the first time Noel Carboni has hit the nail on the head of a topic once more – Microsoft’s six monthly roll out of ‘new’, all singing all dancing versions of Win 10 is a cadence guaranteed to break lots of third-party software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |