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 |
#16
|
|||
|
|||
Creators Update: 0 for 2 :(
On Wed, 01 Nov 2017 02:30:32 -0400 "Paul" wrote in
article C:\Windows\Panther\setupact.log 75,017,518 bytes --- Redmond time The "error" is not right at the end of that file, because the "unroll" of the install also gets logged. There is also potentially a setuperr.log. How to interpret, is documented here. https://technet.microsoft.com/en-us/...(v=ws.10).aspx Thanks for the link! It makes sense of the numerous logs. I'm looking at them now. |
Ads |
#17
|
|||
|
|||
Creators Update: 0 for 2 :(
On Wed, 1 Nov 2017 17:56:48 -0400 "Jason" wrote in
article I have tried this. No luck. So have the MS support people - they gathered a ton of log files and will let me know what they find. Another round with "support" and another failure. This time, they spotted an error, 0x80007502, which they claim may require a complete re- installation, a step I am -very- loath to take, given all I have on this machine. I did some searching on that error. One questionnable find suggested a registry entry that I found (but haven't touched!) It's Group Policy setting: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\WindowsUpdate\ DisableOSUpgrade REG_DWORD (1) ! I am sufficiently ignorant of such things to dare change it, but it surely aroused my suspicion. Searching for that particular entry online yielded a number of articles, but none mentioned DisableOSUpgrade specifically, so I left everything alone. |
#18
|
|||
|
|||
Creators Update: 0 for 2 :(
Jason wrote:
On Wed, 1 Nov 2017 17:56:48 -0400 "Jason" wrote in article I have tried this. No luck. So have the MS support people - they gathered a ton of log files and will let me know what they find. Another round with "support" and another failure. This time, they spotted an error, 0x80007502, which they claim may require a complete re- installation, a step I am -very- loath to take, given all I have on this machine. I did some searching on that error. One questionnable find suggested a registry entry that I found (but haven't touched!) It's Group Policy setting: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\WindowsUpdate\ DisableOSUpgrade REG_DWORD (1) ! I am sufficiently ignorant of such things to dare change it, but it surely aroused my suspicion. Searching for that particular entry online yielded a number of articles, but none mentioned DisableOSUpgrade specifically, so I left everything alone. That setting was being used, to prevent Windows 7 from being "upgraded" to Windows 10, during the "Free Upgrade Era". I don't see a reason why it wouldn't stop other from-to combos as well. But if that was the case, it shouldn't get part way along the upgrade, and then tip over. It should instead refuse to start an install. I've "forced" a number of my Win10 installations. And the reason I have to do that, is I know there is no graphics driver update available for the GPU. To do that, you could: 1) Download a 1709 DVD. Make sure it matches the bitness of your current OS. If the System control panel says you're running an x64 OS, then you'd want to download x64 media. You can do the download from your Win10 machine. If you store the file on a USB stick, that's one less thing clogging up C: . When you start an install, the contents are going to be copied to the internal drive anyway, so you cannot avoid all space consumption by doing it that way, 2) You don't absolutely need to burn a DVD, but the DVD comes in handy for emergencies. Some machines don't have an optical drive, and that's when mounting the ISO comes in handy. Modern Windows can mount both ISO and VHD/VHDX files as virtual storage devices. I think there's even a scheme where you can boot off a VHD (as long as it's properly entered in the BCD file). 3) Mount the downloaded ISO file, as a virtual DVD. Then, you should see a new optical drive, in File Explorer. Run Setup.exe off the File Explorer window which displays the virtual DVD contents. As long as you record the full key path for the DisableOSUpgrade, you can always put it back later. That setting should be reasonably independent of other stuff. There are actually, a number of keys that can block the installation, including the operation of "reverting" the OS. That's been known to block a re-install of the same version. But if you're using media for a newer version, then that should work. The "reverting rule" is so a user will not be placed into an upgrade loop, where the user reverts over and over again, and the OS won't stop upgrading :-) But if a later version comes in, then it's fair game for Windows Update to try to install the newer version. Paul |
#19
|
|||
|
|||
Creators Update: 0 for 2 :(
"Jason" wrote in message ... On Wed, 1 Nov 2017 17:56:48 -0400 "Jason" wrote in article I have tried this. No luck. So have the MS support people - they gathered a ton of log files and will let me know what they find. Another round with "support" and another failure. This time, they spotted an error, 0x80007502, which they claim may require a complete re- installation, a step I am -very- loath to take, given all I have on this machine. I did some searching on that error. One questionnable find suggested a registry entry that I found (but haven't touched!) It's Group Policy setting: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\WindowsUpdate\ DisableOSUpgrade REG_DWORD (1) ! I am sufficiently ignorant of such things to dare change it, but it surely aroused my suspicion. Searching for that particular entry online yielded a number of articles, but none mentioned DisableOSUpgrade specifically, so I left everything alone. Jason, In Paul's post he noted that not having a driver for a GPU....etc.... Read that part carefully. Did you even try upgrading using just a *generic* video driver and not the NVidia? And hopefully, you have checked in the Advanced section of the Windows Updates screen and made sure that disable feature updates was not checked. I'm not on a Win10 system at the moment so I'm not sure of the exact wording but you'll get the idea once you see it. Bob S. |
#20
|
|||
|
|||
Creators Update: 0 for 2 :(
On Wed, 8 Nov 2017 00:35:38 -0500 "Bob_S" wrote in
article In Paul's post he noted that not having a driver for a GPU....etc.... Read that part carefully. Did you even try upgrading using just a *generic* video driver and not the NVidia? Yes. I did try that. Same result. And hopefully, you have checked in the Advanced section of the Windows Updates screen and made sure that disable feature updates was not checked. Yup. "Defer feature updates" is what I think you refer to. |
#21
|
|||
|
|||
Creators Update: 0 for 2 :(
Well, after six sessions with MS Support steering the ship remotely,
they've given up. The issue was escalated to "Tier 1 - the engineers". They suggested several things: running the update on a system as clean as could be - no unnecessary services, startup items, etc; uninstalling a handful of old apps; updating drivers, and using the generic video driver instead of the Nvidia one. (There is a TON of traffic on Nvidia's site about upgrade issues seemingly caused by their software. It's almost enough to convince me to swap out the card for an AMD one, but I don't have one and that's too big a hassle...) Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. As I've told Support all along, I've little interest in new features. I just want security updates. From what I read of the timeline for Windows-as-a-Service, it looks like my version falls off the edge early next year - no more updates. |
#22
|
|||
|
|||
Creators Update: 0 for 2 :(
On 11/13/2017 11:08 AM, Jason wrote:
Well, after six sessions with MS Support steering the ship remotely, they've given up. The issue was escalated to "Tier 1 - the engineers". They suggested several things: running the update on a system as clean as could be - no unnecessary services, startup items, etc; uninstalling a handful of old apps; updating drivers, and using the generic video driver instead of the Nvidia one. (There is a TON of traffic on Nvidia's site about upgrade issues seemingly caused by their software. It's almost enough to convince me to swap out the card for an AMD one, but I don't have one and that's too big a hassle...) Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. As I've told Support all along, I've little interest in new features. I just want security updates. From what I read of the timeline for Windows-as-a-Service, it looks like my version falls off the edge early next year - no more updates. You've spent enough time ****ing around with this problem to have done a clean install and reinstall of all your apps and have a perfectly clean system. Doesn't your head hurt from banging it against a wall? Rene |
#23
|
|||
|
|||
Creators Update: 0 for 2 :(
On 13/11/2017 17:08, Jason wrote:
Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. How about inserting a completely new HD and start again. Your old HD can remain as it is in an enclosure so that in the future you can try something else with it. In terms of time and money this is the best way forward considering you have un-replaceable data on the HD that you can't backup despite having tons of portable HDs in your repository. Keep your old HD in a safe place until you get fed up looking after it. In my case this is normally after 3 days!!. -- With over 500 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#24
|
|||
|
|||
Creators Update: 0 for 2 :(
On Mon, 13 Nov 2017 11:24:03 -0600 "Rene Lamontagne"
wrote in article You've spent enough time ****ing around with this problem to have done a clean install and reinstall of all your apps and have a perfectly clean system. Far from true. Thanks for the helpful remark. |
#25
|
|||
|
|||
Creators Update: 0 for 2 :(
On Tue, 14 Nov 2017 00:06:24 +0000 "Good Guy"
wrote in article On 13/11/2017 17:08, Jason wrote: Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. How about inserting a completely new HD and start again. Your old HD can remain as it is in an enclosure so that in the future you can try something else with it. In terms of time and money this is the best way forward considering you have un-replaceable data on the HD that you can't backup despite having tons of portable HDs in your repository. Keep your old HD in a safe place until you get fed up looking after it. In my case this is normally after 3 days!!. I do not have irreplacable data - it's well backed up (externally), so that's not an issue, and I can restore the system from it, so trying a clean install is an option. I'm concerned that I'll run into the same problem again with some incompatibility that MS couldn't nail down that has nothing to do with the software I have installed now. The update could be failing for reasons having to do with hardware. I guess what annoys me most is why the wizards can't give a specific reason for the failure. In years past there were so-called "readiness tools" that would examine your system to see if a new Windows version could be installed. No more? |
#26
|
|||
|
|||
Creators Update: 0 for 2 :(
On 11/13/2017 8:41 PM, Jason wrote:
On Tue, 14 Nov 2017 00:06:24 +0000 "Good Guy" wrote in article On 13/11/2017 17:08, Jason wrote: Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. How about inserting a completely new HD and start again. Your old HD can remain as it is in an enclosure so that in the future you can try something else with it. In terms of time and money this is the best way forward considering you have un-replaceable data on the HD that you can't backup despite having tons of portable HDs in your repository. Keep your old HD in a safe place until you get fed up looking after it. In my case this is normally after 3 days!!. I do not have irreplacable data - it's well backed up (externally), so that's not an issue, and I can restore the system from it, so trying a clean install is an option. I'm concerned that I'll run into the same problem again with some incompatibility that MS couldn't nail down that has nothing to do with the software I have installed now. The update could be failing for reasons having to do with hardware. I guess what annoys me most is why the wizards can't give a specific reason for the failure. In years past there were so-called "readiness tools" that would examine your system to see if a new Windows version could be installed. No more? Wondering if you have tried the "Update Assistant". https://www.microsoft.com/en-us/soft...load/windows10 Ben |
#27
|
|||
|
|||
Creators Update: 0 for 2 :(
On 11/13/2017 7:41 PM, Jason wrote:
On Tue, 14 Nov 2017 00:06:24 +0000 "Good Guy" wrote in article On 13/11/2017 17:08, Jason wrote: Their final suggestion, 'tho they'll leave the issue open for a while, is installation from scratch. That would be a gigantic headache, but I may do it sometime. How about inserting a completely new HD and start again. Your old HD can remain as it is in an enclosure so that in the future you can try something else with it. In terms of time and money this is the best way forward considering you have un-replaceable data on the HD that you can't backup despite having tons of portable HDs in your repository. Keep your old HD in a safe place until you get fed up looking after it. In my case this is normally after 3 days!!. I do not have irreplacable data - it's well backed up (externally), so that's not an issue, and I can restore the system from it, so trying a clean install is an option. I'm concerned that I'll run into the same problem again with some incompatibility that MS couldn't nail down that has nothing to do with the software I have installed now. The update could be failing for reasons having to do with hardware. I guess what annoys me most is why the wizards can't give a specific reason for the failure. In years past there were so-called "readiness tools" that would examine your system to see if a new Windows version could be installed. No more? Very frustrating problem Indeed,, I had one of my friends machines over to look for much the same reason a couple weeks ago and spent a fair amount of time trying to get it updated to 1703, Having no luck with it I finally decided to bite the bullet and do a good backup on Macrium Reflect and save all his email and photo stuff to USB drives. I made sure he had his relevant program disks and made a list of all installed software. and drivers. Then wiped the disk knowing I could go back to where we were if things didn't work. Well in about 4 hours I had the system up and running and reinstalled his 4 or 5 major programs, The little programs and utilities he could install at his leisure. So what seemed a gargantuan job wasn't half as bad as anticipated and he now has a faster cleaner system without all that Win 7 and 8 cruft dragging along. HTH Rene |
#28
|
|||
|
|||
Creators Update: 0 for 2 :(
On Mon, 13 Nov 2017 21:25:09 -0500 "Ben Myers"
wrote in article Wondering if you have tried the "Update Assistant". https://www.microsoft.com/en-us/soft...load/windows10 Ben I have. So did the support people. Didn't work |
#29
|
|||
|
|||
Creators Update: 0 for 2 :(
Jason wrote:
On Mon, 13 Nov 2017 21:25:09 -0500 "Ben Myers" wrote in article Wondering if you have tried the "Update Assistant". https://www.microsoft.com/en-us/soft...load/windows10 Ben I have. So did the support people. Didn't work That method should try to stage drivers, before the install begins. Whereas if you run setup.exe off the downloaded DVD, it should try to install anyway. It will use the Microsoft Basic Display Adapter, until while it's sitting in the desktop, it "calls home" and finds a better driver. There are then, fewer dependencies on finishing the install, and potentially a more ugly Device Manager (which can be dealt with, one way or another). Using the DVD and running setup.exe off it, covers situations where the automated upgraders are "blocked by drivers". I'm sure the tier 1 tried all the easy stuff, such as DISM and SFC, to try to clean up the baseline before the install happens. If you did any customization, like move your home directory to D:, move Program Files to E: , that sort of stuff, the Windows Installer is guaranteed to fail. But I don't know if the log shows an appropriate snotty message from MS about it. One other poster, a couple of years ago, was noticing this problem, and I've seen discussion threads on the web about it. But never an apology from MS (they leave the customization trap for you to fall into it). What your experience tells me, is the MS log files really do suck, and the Tier 1 support isn't having an easy time as a result. But you as the owner, probably have a good idea what you've done to it. I can relate a funny story about Win10 install. I originally had a data partition, one where I'd formatted NTFS with 32K clusters, instead of 4K clusters. I didn't even think about it at the time, and did a Win10 install (apparently without the partition being reformatted) right into that partition. Well, everything was fine on the Insider program for maybe 10-15 OS Upgrades. Then one day, wham... dead. The next OS simply would not install. It took me the longest while, to run fsutil, and notice that the damn cluster size was wrong. Your dude at MS, would never think of looking for something like that. The owner of the computer must have an excellent memory, to remember the "pedigree" of the partition used, and remember "Doh, wrong cluster size" at a later date :-) Paul |
#30
|
|||
|
|||
Creators Update: 0 for 2 :(
On Tue, 14 Nov 2017 01:11:13 -0500, Paul wrote:
I can relate a funny story about Win10 install. I originally had a data partition, one where I'd formatted NTFS with 32K clusters, instead of 4K clusters. I didn't even think about it at the time, and did a Win10 install (apparently without the partition being reformatted) right into that partition.... Why would the installer worry about the cluster size? Files don't care, do they? |
Thread Tools | |
Display Modes | Rate This Thread |
|
|