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
|
|||
|
|||
Creators Fall update problem
I have an HP G72 laptop computer that refuses to install the Creators
Fall update. I attempted to do the install from a DVD I made and ironically used on another G72 and a desktop successfully. Both G72's have identical hardware as far as the bios, MB, RAM and HD are concerned. The failure occurs during the restart efforts during the installation and locks up the computer. Pressing the power switch to turn it off and again start it continues the installation until it fails again at about 90%, when it gives an error message "0xC1900101-0x4000D Migrate_data operation." https://answers.microsoft.com/en-us/...a-a3365989b09b I searched for the error message and found many others who have also encountered the same problem. Solutions suggested include disabling the AV program, doing a disk cleanup to remove old system files used in prior updates, and starting the computer with the option to disable driver signature verification. I tried every tip I could find and did so three times, failing each time on this computer. Since I already had Win 10 Home Creators version installed on this computer along with many programs, I kept trying to do the upgrade. Out of curiosity to see if there was some hardware problem with the computer, I removed the original HD and installed a different blank HD, then tried to install Win 10 Creators Fall from scratch. When I got to the choice of what version to install, I chose "Home- Single Language" since I had "Home" on the other HD and it was activated. When it finished installing successfully, it said I needed to activate the OS. I was puzzled by this, since the computer had been activated with the "Home" version. When I tried the activation trouble shooter it asked if I wanted to upgrade the version from the previous version they saw had been activated? I chose the "Single Language" version during the installation since I saw no need to have more than one language and it too was a Home version like I had on the other HD. Fearing that upgrading might screw up the installed version on the HD with all the programs installed, I stopped and did not go further with the activation process. I would like to know if anyone else encountered the problems and error code I got when the Creators Fall upgrade failed, and if they found a solution? Also, if I had chosen to "Upgrade" and activate due to the "Home- Single Language" edition I erroneously chose, would I be charged for the upgrade or have the "Home" version on the other HD disabled as a result? I reinstalled the original HD and it is running the Creators version again successfully, but I fear eventually it will attempt to do the Creators Fall update via the automatic download and again fail. Thanks. |
Ads |
#2
|
|||
|
|||
Creators Fall update problem
Wolf K wrote:
Interesting story. No, I haven't had that precise issue with an upgrade, but I have had weird issues upgrading with other machines and other Windows versions. Eg, a "hardware upgrade" worked fine on one machine, but disabled the mouse on another. Installing a brand new blank HDD in essence means that you built a brand new machine, with no history of previous use on the HD. Hence the activation request, etc. Most of what you say is true, but since the activation was via digital license, they key on the hardware used during the initial installation. I had a friend who had a crash on his computer that had contained Win 10 activated digitally. Finally I wiped his HD clean and installed Win 10 from a DVD. It recognized that the computer had been activated and did so again without asking. I think it indicates that the old HD has registry errors and/or detritus from uninstalling programs, lost temporary files, file fragments, unclosed files, etc. If so, a Disk Cleanup and a mild registry cleaner before upgrading should get rid of such stuff. Good luck. I think you are correct about the registry, but I was hesitant to mess with the registry for fear of making the working version not work. If I encounter this problem again I will take a chance on such a program to clean the registry. Should you allow the Fall update? Posts here indicate that Creator updates have been buggy, so I would wait for the one after that, even after Disk Cleanup. IIRC, there are ways of preventing W10 Home from updating, ask for that specifically. Good luck. How do you refuse the update for Win 10? I thought you were at their mercy on updates? Thanks for your comments. |
#3
|
|||
|
|||
Creators Fall update problem
On Wed, 15 Nov 2017 09:00:23 -0700, KenW wrote:
Registry cleaners are VERY dangerous. I learned my lesson years ago and only use one to search for settings I want to remove. Backups help avoid risks. |
#4
|
|||
|
|||
Creators Fall update problem
On Wed, 15 Nov 2017 09:33:57 -0600, Ken wrote:
Wolf K wrote: Interesting story. No, I haven't had that precise issue with an upgrade, but I have had weird issues upgrading with other machines and other Windows versions. Eg, a "hardware upgrade" worked fine on one machine, but disabled the mouse on another. Installing a brand new blank HDD in essence means that you built a brand new machine, with no history of previous use on the HD. Hence the activation request, etc. Most of what you say is true, but since the activation was via digital license, they key on the hardware used during the initial installation. I had a friend who had a crash on his computer that had contained Win 10 activated digitally. Finally I wiped his HD clean and installed Win 10 from a DVD. It recognized that the computer had been activated and did so again without asking. I think it indicates that the old HD has registry errors and/or detritus from uninstalling programs, lost temporary files, file fragments, unclosed files, etc. If so, a Disk Cleanup and a mild registry cleaner before upgrading should get rid of such stuff. Good luck. I think you are correct about the registry, but I was hesitant to mess with the registry for fear of making the working version not work. If I encounter this problem again I will take a chance on such a program to clean the registry. I strongly recommend against *all* registry cleaners. They are *all* snake oil. Cleaning of the registry isn't needed and is dangerous. Leave the registry alone and don't use any registry cleaner. Despite what many people think, and what vendors of registry cleaning software try to convince you of, having unused registry entries doesn't really hurt you. The risk of a serious problem caused by a registry cleaner erroneously removing an entry you need is far greater than any potential benefit it may have. Read https://support.microsoft.com/en-us/kb/2563254 http://www.howtogeek.com/171633/why-...r-fix-crashes/ https://blog.malwarebytes.org/social...tal-snake-oil/ and also http://blogs.technet.com/markrussino...t-of-life.aspx https://support.microsoft.com/en-us/kb/2563254 You also might want to read the section on the CCleaner Registry Cleaner he http://www.howtogeek.com/113382/how-...9-tips-tricks/ Let me point out that neither I nor anyone else who warns against the use of registry cleaners has ever said that they always cause problems. If they always caused problems, they would disappear from the market almost immediately. Many people have used a registry cleaner and never had a problem with it. Rather, the problem with a registry cleaner is that it carries with it the substantial *risk* of having a problem. And since there is no benefit to using a registry cleaner, running that risk is a very bad bargain. |
#5
|
|||
|
|||
Creators Fall update problem
On Wed, 15 Nov 2017 18:32:32 +0000, mechanic
wrote: On Wed, 15 Nov 2017 09:00:23 -0700, KenW wrote: Registry cleaners are VERY dangerous. I learned my lesson years ago and only use one to search for settings I want to remove. Backups help avoid risks. Helps? Yes. Avoids? No. If using a registry cleaner results in an unbootable computer, the backup will not have helped much. |
#6
|
|||
|
|||
Creators Fall update problem
Ken" wrote in message news
I chose the "Single Language" version during the installation since I saw no need to have more than one language and it too was a Home version like I had on the other HD Home Single Language has its own unique Product Key. i.e. A product key provided with Win10 Home(retail, OEM media, or OEM key on firmware) is not 'Home Single Language'. A device with a digital license on MSFT servers for Win10 Home will not activate a Home Single Language install. i.e. you chose the wrong option -- ....w¡ñ§±¤ñ msft mvp 2007-2016, insider mvp 2016-2018 |
#7
|
|||
|
|||
Creators Fall update problem
"Wolf K" wrote in message ...
Installing a brand new blank HDD in essence means that you built a brand new machine, with no history of previous use on the HD. Hence the activation request, etc.. The new blank HDD was not the reason for the activation request. Using Home 'Single Language' was. Win10 Home SL is not the same as Win10 Home. - Home SL has its own product key and unless a Home SL digital license existed for the device on MSFT servers the user must provide a Home SL product key to activate. -- ....w¡ñ§±¤ñ msft mvp 2007-2016, insider mvp 2016-2018 |
#8
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On Wed, 15 Nov 2017 15:28:03 -0500, Wolf K
wrote: On 2017-11-15 15:24, Wolf K wrote: On 2017-11-15 13:44, Ken Blake wrote: I strongly recommend against*all*Â* registry cleaners. They are*all* snake oil. Cleaning of the registry isn't needed and is dangerous. Leave the registry alone and don't use any registry cleaner. Despite what many people think, and what vendors of registry cleaning software try to convince you of, having unused registry entries doesn't really hurt you. The risk of a serious problem caused by a registry cleaner erroneously removing an entry you need is far greater than any potential benefit it may have. FWIW, I've use CCleaner's reg cleaner every now and then. It's very mild, has never trashed anything I needed. It's useful for getting rid of obsolete keys, the same ones that Revo Uninstall finds after the program's uninstall has done its work. YMMV. It's probably the safest of all registry cleaners. But that doesn't it's risk-free. And there's really no particular advantage to getting rid of obsolete keys. |
#9
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On Wed, 15 Nov 2017 14:11:09 -0700, Ken Blake
wrote: On Wed, 15 Nov 2017 15:28:03 -0500, Wolf K wrote: On 2017-11-15 15:24, Wolf K wrote: On 2017-11-15 13:44, Ken Blake wrote: I strongly recommend against*all** registry cleaners. They are*all* snake oil. Cleaning of the registry isn't needed and is dangerous. Leave the registry alone and don't use any registry cleaner. Despite what many people think, and what vendors of registry cleaning software try to convince you of, having unused registry entries doesn't really hurt you. The risk of a serious problem caused by a registry cleaner erroneously removing an entry you need is far greater than any potential benefit it may have. FWIW, I've use CCleaner's reg cleaner every now and then. It's very mild, has never trashed anything I needed. It's useful for getting rid of obsolete keys, the same ones that Revo Uninstall finds after the program's uninstall has done its work. YMMV. It's probably the safest of all registry cleaners. But that doesn't it's risk-free. And there's really no particular advantage to getting rid of obsolete keys. I create an image of C: before the Tuesday update. That tests the last update for a month and so far so good. KenW |
#10
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On Wed, 15 Nov 2017 14:11:09 -0700, Ken Blake
wrote: On Wed, 15 Nov 2017 15:28:03 -0500, Wolf K wrote: On 2017-11-15 15:24, Wolf K wrote: On 2017-11-15 13:44, Ken Blake wrote: I strongly recommend against*all** registry cleaners. They are*all* snake oil. Cleaning of the registry isn't needed and is dangerous. Leave the registry alone and don't use any registry cleaner. Despite what many people think, and what vendors of registry cleaning software try to convince you of, having unused registry entries doesn't really hurt you. The risk of a serious problem caused by a registry cleaner erroneously removing an entry you need is far greater than any potential benefit it may have. FWIW, I've use CCleaner's reg cleaner every now and then. It's very mild, has never trashed anything I needed. It's useful for getting rid of obsolete keys, the same ones that Revo Uninstall finds after the program's uninstall has done its work. YMMV. It's probably the safest of all registry cleaners. But that doesn't it's risk-free. And there's really no particular advantage to getting rid of obsolete keys. CCleaner Pro on my side. I've been using it for years and have yet to face any problem with it. Regardless of what some expert says, my own experience with the registry (since Windows 95 beta) has been that an uncleaned one will indeed slow the computer down and you'll face more issues by NOT cleaning it of unnecessary keys. |
#11
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On Wed, 15 Nov 2017 19:28:10 -0500, Doomsdrzej wrote:
On Wed, 15 Nov 2017 14:11:09 -0700, Ken Blake wrote: On Wed, 15 Nov 2017 15:28:03 -0500, Wolf K wrote: On 2017-11-15 15:24, Wolf K wrote: On 2017-11-15 13:44, Ken Blake wrote: I strongly recommend against*all*Â* registry cleaners. They are*all* snake oil. Cleaning of the registry isn't needed and is dangerous. Leave the registry alone and don't use any registry cleaner. Despite what many people think, and what vendors of registry cleaning software try to convince you of, having unused registry entries doesn't really hurt you. The risk of a serious problem caused by a registry cleaner erroneously removing an entry you need is far greater than any potential benefit it may have. FWIW, I've use CCleaner's reg cleaner every now and then. It's very mild, has never trashed anything I needed. It's useful for getting rid of obsolete keys, the same ones that Revo Uninstall finds after the program's uninstall has done its work. YMMV. It's probably the safest of all registry cleaners. But that doesn't it's risk-free. And there's really no particular advantage to getting rid of obsolete keys. CCleaner Pro on my side. I've been using it for years and have yet to face any problem with it. Regardless of what some expert says, my own experience with the registry (since Windows 95 beta) has been that an uncleaned one will indeed slow the computer down and you'll face more issues by NOT cleaning it of unnecessary keys. My experience is completely different from yours. |
#12
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On 15 Nov 2017, Wolf K wrote in
alt.comp.os.windows-10: I surmise that it depends on how much software you've un/installed. On a relatively clean system, cleaning the registry shouldn't be necessary. If you've had experience with indexed databases, you know that they can be *huge*, giga- or -terabytes large, and if your query uses the index properly, queries are lightning fast. The registry is such a database, and I don't think there would be a human-detectable lag in normal conditions. |
#13
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On 16/11/2017 00:28, Doomsdrzej wrote:
CCleaner Pro on my side. I've been using it for years and have yet to face any problem with it. It looks like you have a higher IQ than those idiots who blindly and religiously say that Registry Cleaners are bad and carry risks. Those people should never be allowed to make any changes on their machines. It is rumoured that some of them have never formatted a HD in their life for fear that they may not be able to install the operating system ever again!!! The old age is catching up with them and so they become senile progressively. -- With over 500 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#14
|
|||
|
|||
Registry Cleaners ( Creators Fall update problem)
On 11/15/2017 7:35 PM, Nil wrote:
On 15 Nov 2017, Wolf K wrote in alt.comp.os.windows-10: I surmise that it depends on how much software you've un/installed. On a relatively clean system, cleaning the registry shouldn't be necessary. If you've had experience with indexed databases, you know that they can be *huge*, giga- or -terabytes large, and if your query uses the index properly, queries are lightning fast. The registry is such a database, and I don't think there would be a human-detectable lag in normal conditions. Registry cleaners are like Oven cleaners. :-) :-) |
#15
|
|||
|
|||
Creators Fall update problem
Wolf K wrote:
On 2017-11-15 15:03, ...winston wrote: "Wolf K" wrote in message ... Installing a brand new blank HDD in essence means that you built a brand new machine, with no history of previous use on the HD. Hence the activation request, etc.. The new blank HDD was not the reason for the activation request. Using Home 'Single Language' was. Win10 Home SL is not the same as Win10 Home. - Home SL has its own product key and unless a Home SL digital license existed for the device on MSFT servers the user must provide a Home SL product key to activate. Thanks for the correction/clarification. Anyhow, it looks like Activation saw the machine as new build. Also seems that OP did not in fact reinstall what he had. yw. The Activation server responded due to one or more of the following conditions. 1. a valid digital license associated with the device for the installed edition did not exist on the server 2. a valid product key for the installed edition on the device was not provided Additionally by prompting/asking if desiring to upgrade - it recognized the device having a digital license for a different installed edition. -- .....w¡ñ§±¤ñ msft mvp 2007-2016, insider mvp 2016-2018 |
Thread Tools | |
Display Modes | Rate This Thread |
|
|