If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
1709 update discovery
MS "support" gave up trying to help me install 1709 atop 1607. They could
not tell me if the issue was caused by hardware or software and recommended a "clean" install - i.e., you get to install EVERYTHING again, a daunting proposition. So I set the idea aside. Now, every time I boot, Windows dutifully tries installing the update again. I think I can throttle that behavior by disabling Update. Today, with a fresh full image backup, I tried a clean install and it went perfectly. So hardware isn't the issue (unless it's a driver that doesn't cooperate but which didn't get 'touched' during my experiment). So I'm tempted to re-open the case with MS with this new info. When they gave up before, I asked what seemed like a reasonable question for which they had no answer: at some point Setup quit. It quit for a reason. What's the reason?? They couldn't say. Now I think hardware is NOT the reason and wonder if it's worth another telephone marathon with them. |
Ads |
#2
|
|||
|
|||
1709 update discovery
"Jason" wrote in message ... MS "support" gave up trying to help me install 1709 atop 1607. They could not tell me if the issue was caused by hardware or software and recommended a "clean" install - i.e., you get to install EVERYTHING again, a daunting proposition. So I set the idea aside. Now, every time I boot, Windows dutifully tries installing the update again. I think I can throttle that behavior by disabling Update. Today, with a fresh full image backup, I tried a clean install and it went perfectly. So hardware isn't the issue (unless it's a driver that doesn't cooperate but which didn't get 'touched' during my experiment). So I'm tempted to re-open the case with MS with this new info. When they gave up before, I asked what seemed like a reasonable question for which they had no answer: at some point Setup quit. It quit for a reason. What's the reason?? They couldn't say. Now I think hardware is NOT the reason and wonder if it's worth another telephone marathon with them. Jason, Probably not worth the aggravation since they didn't have an answer before. I'll add this tidbit which you can easily verify. The fresh Win10 install, installed it's own (generic) drivers as needed to get the system up and running but the driver(s) it installs may not be optimal for the hardware. Drivers for graphics, NIC's, and USB devices are usually generic until Win10 is fully updated which may update to OEM drivers provided to MS. You should check the manufacturers site to see if they have Win10 drivers and install those. If you have a problem with a driver from a manufacturer, you can roll-back to the previous version. Open Device Manager and open the tree for each device. On *each and every* entry in the sub-tree menus, right-click and select "Update Driver Software". The operative word is "each". There are a lot of entries but do every one of them. Some may take a minute or two to verify. What may have happened is that Win10 stayed with some drivers that were previously installed during the upgrade tries and that could have been the problem. I wrote a post several months back about doing driver updates before upgrading. Bob S. |
#3
|
|||
|
|||
1709 update discovery
Jason wrote:
MS "support" gave up trying to help me install 1709 atop 1607. They could not tell me if the issue was caused by hardware or software and recommended a "clean" install - i.e., you get to install EVERYTHING again, a daunting proposition. So I set the idea aside. Now, every time I boot, Windows dutifully tries installing the update again. I think I can throttle that behavior by disabling Update. Today, with a fresh full image backup, I tried a clean install and it went perfectly. So hardware isn't the issue (unless it's a driver that doesn't cooperate but which didn't get 'touched' during my experiment). So I'm tempted to re-open the case with MS with this new info. When they gave up before, I asked what seemed like a reasonable question for which they had no answer: at some point Setup quit. It quit for a reason. What's the reason?? They couldn't say. Now I think hardware is NOT the reason and wonder if it's worth another telephone marathon with them. I guess it depends on whether you think they'll learn anything from the experience. ******* You could return to your original experiments and go through the logs. There is some information here. https://docs.microsoft.com/en-us/win...upgrade-errors Paul |
#4
|
|||
|
|||
1709 update discovery
On 4/2/2018 10:18, Jason wrote:
So I'm tempted to re-open the case with MS with this new info. When they gave up before, I asked what seemed like a reasonable question for which they had no answer: at some point Setup quit. It quit for a reason. What's the reason?? They couldn't say. Now I think hardware is NOT the reason and wonder if it's worth another telephone marathon with them. Phone/email support has limitations. It is not like they sitting in front of your computers. Um... how about you give them remote access to your Window$? -- @~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!! / v \ Simplicity is Beauty! /( _ )\ May the Force and farces be with you! ^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3 不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA): http://www.swd.gov.hk/tc/index/site_...sub_addressesa |
#5
|
|||
|
|||
1709 update discovery
Mr. Man-wai Chang wrote:
On 4/2/2018 10:18, Jason wrote: So I'm tempted to re-open the case with MS with this new info. When they gave up before, I asked what seemed like a reasonable question for which they had no answer: at some point Setup quit. It quit for a reason. What's the reason?? They couldn't say. Now I think hardware is NOT the reason and wonder if it's worth another telephone marathon with them. Phone/email support has limitations. It is not like they sitting in front of your computers. Um... how about you give them remote access to your Window$? Yes, that's what they do. They tell you what buttons to click, to enable remoting. Then they remote in and check logs and the like. *Free* service is available for a limited set of problem types. An inability to install the OS, is one of the things they support. At the end of the session, you just turn off remoting and you're done. They can't remote in, without help from you on your end. Paul |
#6
|
|||
|
|||
1709 update discovery
Jason wrote:
MS "support" gave up trying to help me install 1709 atop 1607. They could not tell me if the issue was caused by hardware or software and recommended a "clean" install - i.e., you get to install EVERYTHING again, a daunting proposition. As you should know by now, you should have backups of Windows, using Macrium Reflect. That way there is no daunting task. |
#7
|
|||
|
|||
1709 update discovery
On 5/2/2018 22:08, John Doe wrote:
As you should know by now, you should have backups of Windows, using Macrium Reflect. That way there is no daunting task. You meant ghosting an installed Window$ partition? I believe a clean install is better, in that you get clean OS. -- @~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!! / v \ Simplicity is Beauty! /( _ )\ May the Force and farces be with you! ^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3 不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA): http://www.swd.gov.hk/tc/index/site_...sub_addressesa |
#8
|
|||
|
|||
1709 update discovery
|
#9
|
|||
|
|||
1709 update discovery
Jason wrote:
er says... Jason wrote: MS "support" gave up trying to help me install 1709 atop 1607. They could not tell me if the issue was caused by hardware or software and recommended a "clean" install - i.e., you get to install EVERYTHING again, a daunting proposition. As you should know by now, you should have backups of Windows, using Macrium Reflect. That way there is no daunting task. I have excellent (Acronis) image backups. That's why I could try installing 10 and then backing it out easily. The daunting task is re- installing all the applications; I use a LOT of them in my work. Huh? You have excellent image backups, that's why you could try installing 10? What??? There is no need to reinstall applications when you have backups of your C drive. Every time you make a backup, you do so before working with the installation. Before restoring a backup, you must copy out any updated data from your programs/work. Then restore. Then reinsert the updated data. Make any noted changes to the installation. Then immediately do a backup before working with the installation. Therefore, you should have pristine backups that include applications and data before you run into trouble. That means you should have a pristine copy of Windows version 1607. No need to reinstall Windows. If your pristine copy of Windows 1607 does not work, you try an installation farther back than that. And so on. |
#10
|
|||
|
|||
1709 update discovery
|
#11
|
|||
|
|||
1709 update discovery
On 08/02/2018 15:36, Jason wrote:
MS couldn't even determine whether it was h/w or s/w causing the failure. I think They were too polite to say that it is the user's ability to use a modern Windows system. They are not allowed to say this specifically; It is not in their scripts! I have ruled out hardware as the problem. In that case you can't rule out your ability to use a Windows 10 system. You need to buy a dummies book and get back to basics. -- With over 600 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|