New
#31
That's good to know, but your post (and the one being replied to) seem to come from an different thread.
Update from 1511 to 1607 failing
-
-
New #32
Looks like I finally succeeded. I really don't know for sure, and it's only been 30 hours, but it's been stable enough that I've made a system image with 1607 to replace 1507. All drives and cables are hooked up again now except one. That's the one which formerly had the Win 10 backup files and some old 8.1 backup as well. The discussion got me wondering if it was causing some conflict during start up, so to be safe I emptied its contents onto a USB stick before starting the update. To be seen... (will mark it as solved when I'm sure). Thanks for the help.
-
New #33
In BIOS > Boot, there are three listings for Windows Boot Manager. I know one works, one sometimes does and the other I haven't tried. Why would there be three listings? Is there a way to remove the extras? If so, is it advisable? Thanks,
-
New #34
It's been a week with 1607 and there's been one continuing problem: about 25% to 100%f restarts don't complete, either in the Restarting screen stage, which is something I'd never seen before, or in the startup stage, running on and on in either case. OTOH, shutting down by case button in those cases and restarting 30-60 seconds later with a "cold" boot invariably restarts ok. Genuine cold boots have started ok the whole time except for maybe a couple of times, when a second try sailed through. I've had the sense that certain (not all) changes to or problems when using a program provoke these restart hangs, but I wouldn't swear that covers all instances. sfc computer scans are mostly coming up clean, disk scans entirely clean and I've run Windows 10 Mgr as well. Any other ideas to try short of a clean install?
Here's an example. After posting the above, I had three straight Restarting screens that hung and required a cold boot. They went as follows:
- Remote install of program as admin
- Foobar crashed while playing a music file and after restarting (too) quickly, there were two entries in Processes (usually none), only one of which would close on End Task (on restart, reinstalled Foobar)
- Foobar played for much longer this time but eventually crashed. Waited, then restarted it but file wouldn't play and second process again wouldn't close. Started XYplorer file manager and tried to copy some files, but it went nonresponding. Was able to close the program process, but the X-Copy one wouldn't close.
- After reboot, Mailwasher Pro had lost it's configuration. After fixing that, ran Windows 10 Manager system component repair, and then restart went fine. Wouldn't be surprised if it Restarting continues to run ok until the next episode like one of the above.
Update: Just ran In-Place Repair Install, so we'll see what happens. Four straight good restarts so far. But a bit of weirdness with opening desktop icons: I have to click directly on the link line under the text or they won't open.Last edited by highstream; 03 Feb 2017 at 19:55.
-
New #35
You could try Tweaking.com Windows repair (free) Tweaking.com - Windows Repair Free/Pro
The first thing it recommends is a disconnection and attempt to clear the system of any electrical residue in the electronic components like capacitors, then a reboot and then going through a boot to safe mode, before running the all in one repairs, which take a bit of time, so leave an hour or two free for this, and heed the warnings when advisable or inadvisable to stop a long process, and how to tell when things have stopped or are still chugging along.
It seems to be thorough and well documented, and uses scripts to run built-in Windows repair processes, not obscure third party programs.
I've found it will make some systems upgradeable again even if Microsoft fix-its and other windows upgrade repairs have failed.
-
New #36
Whatever good that Tweaking program does, and I haven't seen any yet, it sure does a lot of damage.
- It generated the first hung startup in about 10 tries
- It changed dozens of my set default file associations and default programs, which means a good deal of time already spent and a lot more ahead of me. To add to that, each change now takes three to four times as long as it used to.
- It didn't solve the problem with opening desktop icons, which is The pressing problem right now (I'm going to start another thread on this)
I'd be very careful in recommending that program to anyone but rank novices, i.e., not to someone who knows enough about computing to have made customizations that they don't want this program messing with.
-
New #37
I didn't pay close enough attention to the Tweaking.com instructions, neither in doing a power reset first nor going through the options and eliminating file associations reset and whatever else. I'm going to try again soon.
The two, maybe three problems right now in 1607 post in-place repair install are...
1) restart sometimes hangs in either the closing or startup phases, but then restarts fine after the computer is powered down;
2) desktop icons respond very slowly to a single click, if at all, but typically respond quickly to a double click (setting = single); and
3) (not sure yet if this has been fixed) XYplorer file manager occasionally goes not responding at a certain point and then brings down eveything else with it (I've gone back a couple of versions to find out more, as someone else had a related problem and the developer wants to see it we can isolate it).Last edited by highstream; 08 Feb 2017 at 15:23.
-
New #38
For now, this thread is being continued at Desktop icons not responding on first click, opening other icons
-
-
New #39
Update to 1607 from 1507
Has anyone been able to upgrade from 1607 to 1507 without using WSUS or SCCMLast edited by pcarnes83; 31 May 2017 at 15:09.
-
Quote
Related Discussions
