joddle Posted September 12, 2017 Posted September 12, 2017 I have 3 near identical Dell 755 PCs - all of the used to run W7 and all three got updated to W10 when this was on free offer a while back. Until now all three PCs ran well with no issues and updated as expected. However, with the new W10 update, two of the PCs updated fine but the third would not - in fact the system crashed and wrecked the OS and resulted in blue screens eery time I tried to reboot. Not to worry I decided to put in a new HDD and reinstall from scratch but that's when the issues stared. Every time I try loading W10 (32 or 64 bit) the installation ends with a message saying the system is not compatible - and that is odd as the other two PCs updated and intaled the new W10 just fine. Looking at the three pcs the only real difference I can see is the Bios version on the one not playing is lower (a17) than the Bios version on the other two(A22). So thought this could be the issue. I tried updating the Bios but this fails every and when running the bios update package, when it tries to reset the bios there is a message saying no file in the memory. I also tries updating the bios one version at a time but this still results in the same message. Could the CMOS battery have anything to do with this? or does anyone have any clues as to why I am experiencing this One thing of about this particular PC is that it always takes ages to boot - and stays on a blank screen with just a curser at the top LH corner for a full minute before actually springing into action. This even happens when trying to get into the setup window. Meanwhile I have been able to load up W7 again with no issues but really would like it to be the same as the other PCs and be running W10. Any ideas or thoughts most welcome. Quote
Rustys Posted September 13, 2017 Posted September 13, 2017 (edited) The Media you are using to install Windows 10 were did it come form? Was it created by the system having issues? The CD/DVD reader in the system may be going (if there is one). The media its self may be bad. RAM could be failing Have you tried to reseat the HDD/RAM/DVD power and data cables? Test the RAM. Meanwhile I have been able to load up W7 again with no issues but really would like it to be the same as the other PCs and be running W10.This system still taking ages to boot even with Widows 7? Have you ran a chkdsk /r /f form the admin command prompt? What were the results? How many user-names are on the system? Are they having the same issue? I have 3 near identical Dell 755 PCsWhat is the difference between the one that will not update and the ones that have? Looking at the three pcs the only real difference I can see is the Bios version on the one not playing is lower (a17) than the Bios version on the other two(A22). So thought this could be the issue. I tried updating the Bios but this fails every and when running the bios update package, when it tries to reset the bios there is a message saying no file in the memory. I also tries updating the bios one version at a time but this still results in the same message. Could the CMOS battery have anything to do with this? or does anyone have any clues as to why I am experiencing thisWhich version of Windows? Did you attempt it in Safe Mode? Have you tried resetting the BIOS to defaults and see if it updates? If the CMOS battery is old and needs replaced could be a possibility. Have you tried a reset? Edited September 13, 2017 by Rustys Quote "Confucius could give answer to that. Unfortunately, Confucius not here at moment.”
Starbuck Posted September 13, 2017 Posted September 13, 2017 Just to add to what Rustys has said.... I tried updating the Bios but this fails every and when running the bios update package, when it tries to reset the bios there is a message saying no file in the memory.How are you trying to update the bios? For updating the BIOS, you should go to "support.dell.com" and enter the appropriate service tag number. Then you will see the entire list of possible BIOS updates, drivers, etc. Select the BIOS update that you desire (A22) and from there the website will guide you. Very straight forward process, just follow instructions on the website. I see that the Dell 755 PCs originally came with 2Gb Ram.... have you upgraded the Ram..... 2Gb will struggle with Win10 ( especially 64bit) 4Gb Ram should be your minimum ( 8 Gb is ideal ) Quote Member of:UNITE
joddle Posted September 14, 2017 Author Posted September 14, 2017 (edited) Thanks for those suggestions - and to answer a few of the things raised The PC has 6Gb of ram. I used the Dell site to get the correct bios updates and followed instructions - ( I did the same a while back on the other two PCs and all worked fine) It did have w10 installed and running well and it tired to update to the new creator version and failed WIndows 10 media was downloaded directly from MS site using their tool - have tried USB and CD versions but can only seem to get the new creator version! Can't find an older version of W10 on the MS website to download and try which would be the same as was already on the machine before it crashed and should therefore be compatible as that's what was there before- If that worked the I could rule out loads of other things. The media I then used was downloaded using the MS download tool - I tried both 64 and 32 Bit versions from CD and from USB - same failure message on each that PC not compatible Memory test gives no errors and diagnostics reports nothing odd Tried resetting bios to defaults and still same Not replaced bios battery yet - not sure how to do that and not sure what a "reset" is either Edited September 14, 2017 by joddle Quote
joddle Posted September 14, 2017 Author Posted September 14, 2017 Now managed to get an iso for W10 v1607 so will try loading that onto a new HDD (I will remove and keep the old W7 one just in case!). If that works then I will know for sure if the PC is OK and can then decide if the bios is affecting the loading of v1703 - :) Quote
Rustys Posted September 15, 2017 Posted September 15, 2017 How goes the Windows 10 system? Quote "Confucius could give answer to that. Unfortunately, Confucius not here at moment.”
joddle Posted September 15, 2017 Author Posted September 15, 2017 How goes the Windows 10 system? Waiting for a bit of spare time to do the test - won't be long though - meanwhile in fact I am quite getting used to W7 again :) Quote
joddle Posted September 16, 2017 Author Posted September 16, 2017 Well now had a moment to try a W10 install so put in a scrap HDD which I had lying around and installed an old version of W10 - and hey presto it worked just fine with no errors. So it seems it is only the creator version which says the PC is not compatible. Still not got around the Bios upgrade situation - every time I try it it fails with the same could not find files in memory issue. The cmos battery seems to be holding up the time and other settings OK so does this mean it does not need changing? and is there anything in the MBEX settings that I need to look at? Quote
Starbuck Posted September 16, 2017 Posted September 16, 2017 Hi joddle, Seems that just because your PC was able to receive the Windows 10 Anniversary Update, there's no guarantee it will be ready for the Creators Update. Windows 10 Creators Edition Not Compatible With All Windows 10 Systems How to tell if your PC is eligible for latest version Quote Member of:UNITE
Rustys Posted September 17, 2017 Posted September 17, 2017 and is there anything in the MBEX settings that I need to look at?I really do not remember that much about the MBEX settings. It has been (cough cough) a long time since I have.:o Quote "Confucius could give answer to that. Unfortunately, Confucius not here at moment.”
joddle Posted September 17, 2017 Author Posted September 17, 2017 Still unsure about some of this - the three 755s and the configurations are as follows 2.33gigahertz Intel Core 2 Duo E6550 8 GB Memory - Running w10 1703 - no issues 3.0 gigahertz Intel Core 2 Duo E6850 6GB Memory – Running W10 1703 - no issues 2.0 gigahertz Intel Core 2 Duo E4400 4GB Memory – says incompatible for W10 Creators when I try installing from DVD or from USB but runs earlier W10 fine. From the basic info none of these seem out of spec for the Creators upgrade so I have tried testing compatibility usingthe install media and the command “setup/Compat ScanOnly” Howeverthis seems to want to install W10 but I only want it checked! How far does it run before coming up with the test results and how far can I let itrun before it wrecks my current system? Quote
Starbuck Posted September 17, 2017 Posted September 17, 2017 and is there anything in the MBEX settings that I need to look at? It's not advisable to make any changes unless you know what you are doing. The MEBx is intended for use by advanced users. Making changes in the MEBx configuration program can cause system problems. The MEBx configuration should only be changed from default settings to address a specific need. Intel® Management Engine BIOS Extension (Intel® MEBx) I have tried testing compatibility usingthe install media and the command “setup/Compat ScanOnly” Howeverthis seems to want to install W10 but I only want it checked! How far does it run before coming up with the test resultsAccording to the info.... At the command prompt, type the following command, substituting the drive letter where your installer files are located in place of d:. d:\Setup /Compat ScanOnly Press Enter and follow the setup screens just as if you were performing an upgrade. When you get to the final screen, click Install. The program should end at that point rather than beginning the upgrade. When it does, it writes some information to a file called BlueBox.log, which you'll find in the C:\Windows\Logs\MoSetup folder. Quote Member of:UNITE
joddle Posted September 17, 2017 Author Posted September 17, 2017 (edited) Thanks - I have had another go - was a bit scared it was going to try and reinstall the latest W10 which is what caused the problem I the first place! Anyway cant make head nor tail of the results - posted below - does it say anything about the compatibility? and if so what? 2017-09-17 10:27:25: CommandLine: [F:\Sources\SetupPrep.exe /Compat ScanOnly] 2017-09-17 10:27:25: Opening Box: [F:\Sources\SetupPrep.exe] 2017-09-17 10:27:25: Opening Box Result: [0x0] 2017-09-17 10:27:25: Deleting box result... 2017-09-17 10:27:25: ResumeMode: Not found. 2017-09-17 10:27:25: ResumeMode: [No] 2017-09-17 10:27:25: OsUninstallWarning: Execute file found [FALSE]. 2017-09-17 10:27:25: OsUninstallWarning: [No] 2017-09-17 10:27:25: Checking cleanup registry value... 2017-09-17 10:27:25: Skipping cleanup. 2017-09-17 10:27:25: Cleaning working dir... 2017-09-17 10:27:25: Cleaning alternate storage paths... 2017-09-17 10:27:25: Cleaning MoSetup Volatile key... 2017-09-17 10:27:25: Cleaning MoSetup RegBackup key... 2017-09-17 10:27:25: Removing CorrelationVector registry value... 2017-09-17 10:27:25: Removing cleanup registry value... 2017-09-17 10:27:25: Creating path (with ACL): [C:\$WINDOWS.~BT]... 2017-09-17 10:27:25: Creating path: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 10:27:27: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] with command-line [/install /Media /ProcessId 1956 /InstallFile "F:\Sources\Install.wim" "/Compat" "ScanOnly" /MediaPath "F:" /SuccessId 8203030a-3e64-4c2d-9500-01e10b05e709] in Session: [-1] 2017-09-17 10:27:27: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] [/install /Media /ProcessId 1956 /InstallFile "F:\Sources\Install.wim" "/Compat" "ScanOnly" /MediaPath "F:" /SuccessId 8203030a-3e64-4c2d-9500-01e10b05e709] from []! 2017-09-17 10:27:27: Waiting for process events... 2017-09-17 10:29:54: Process exit code: [0x800704C7] 2017-09-17 10:29:54: LaunchProcessInSession: Error = 0x800704C7 2017-09-17 10:29:54: LaunchProcessInSession returned: [0x800704C7] 2017-09-17 10:29:54: Checking cleanup registry value... 2017-09-17 10:29:54: Performing cleanup level: [0x1] 2017-09-17 10:29:54: Populating preservation paths... 2017-09-17 10:29:54: Acquiring privileges... 2017-09-17 10:29:54: Cleaning install folder... 2017-09-17 10:29:54: Cleaning folder: [C:\$WINDOWS.~BT\Boot]... 2017-09-17 10:29:54: Cleaning folder: [C:\$WINDOWS.~BT\Efi]... 2017-09-17 10:29:54: Protecting folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 10:29:54: Cleaning parent folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 10:29:54: Protecting folder: [C:\$WINDOWS.~BT\Sources\Diagnostics]... 2017-09-17 10:29:54: Cleaning folder: [C:\$WINDOWS.~BT\Sources\dlmanifests]... 2017-09-17 10:29:55: Cleaning folder: [C:\$WINDOWS.~BT\Sources\es-es]... 2017-09-17 10:29:55: Cleaning folder: [C:\$WINDOWS.~BT\Sources\etwproviders]... 2017-09-17 10:29:55: Cleaning folder: [C:\$WINDOWS.~BT\Sources\inf]... 2017-09-17 10:29:55: Cleaning folder: [C:\$WINDOWS.~BT\Sources\migration]... 2017-09-17 10:29:55: Protecting folder: [C:\$WINDOWS.~BT\Sources\Panther]... 2017-09-17 10:29:55: Cleaning folder: [C:\$WINDOWS.~BT\Sources\replacementmanifests]... 2017-09-17 10:29:56: Cleaning folder: [C:\$WINDOWS.~BT\Sources\sxs]... 2017-09-17 10:29:56: Cleaning MoSetup Volatile key... 2017-09-17 10:29:56: Cleaning MoSetup RegBackup key... 2017-09-17 10:29:56: Removing CorrelationVector registry value... 2017-09-17 10:29:56: Removing cleanup registry value... 2017-09-17 10:29:56: Path successfully cleaned! 2017-09-17 10:29:56: MainHr: Error = 0x800704C7 2017-09-17 10:29:56: wWinMain: Error = 0x800704C7 2017-09-17 13:00:36: CommandLine: [F:\Sources\SetupPrep.exe /Compat ScanOnly] 2017-09-17 13:00:36: Opening Box: [F:\Sources\SetupPrep.exe] 2017-09-17 13:00:36: Opening Box Result: [0x0] 2017-09-17 13:00:36: Deleting box result... 2017-09-17 13:00:36: ResumeMode: Not found. 2017-09-17 13:00:36: ResumeMode: [No] 2017-09-17 13:00:36: OsUninstallWarning: Execute file found [FALSE]. 2017-09-17 13:00:36: OsUninstallWarning: [No] 2017-09-17 13:00:36: Checking cleanup registry value... 2017-09-17 13:00:36: Checking SetupHost result value... 2017-09-17 13:00:36: SetupHost result missing! Forcing full cleanup... 2017-09-17 13:00:36: Performing cleanup level: [0x1] 2017-09-17 13:00:36: Populating preservation paths... 2017-09-17 13:00:36: Acquiring privileges... 2017-09-17 13:00:36: Cleaning install folder... 2017-09-17 13:00:37: Protecting folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 13:00:37: Cleaning parent folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 13:00:37: Protecting folder: [C:\$WINDOWS.~BT\Sources\Diagnostics]... 2017-09-17 13:00:37: Protecting folder: [C:\$WINDOWS.~BT\Sources\Panther]... 2017-09-17 13:00:37: Cleaning MoSetup Volatile key... 2017-09-17 13:00:37: Cleaning MoSetup RegBackup key... 2017-09-17 13:00:37: Removing CorrelationVector registry value... 2017-09-17 13:00:37: Removing cleanup registry value... 2017-09-17 13:00:37: Path successfully cleaned! 2017-09-17 13:00:37: Preserve working path: [No] 2017-09-17 13:00:37: Cleaning working dir... 2017-09-17 13:00:37: Attempting to close previous ETW session... 2017-09-17 13:00:37: Attempting to clean mounted registry hives... 2017-09-17 13:00:37: Attempting to clean mounted SafeOs image... 2017-09-17 13:00:37: Attempting to preserve existing logs... 2017-09-17 13:00:37: Creating path: [C:\Windows\Panther\NewOs\Panther]... 2017-09-17 13:00:37: Copying [C:\$WINDOWS.~BT\Sources\Panther] -> [C:\Windows\Panther\NewOs\Panther]... 2017-09-17 13:00:37: Cleaning working path: [C:\$WINDOWS.~BT]... 2017-09-17 13:00:37: Cleaning alternate storage paths... 2017-09-17 13:00:37: Cleaning MoSetup Volatile key... 2017-09-17 13:00:37: Cleaning MoSetup RegBackup key... 2017-09-17 13:00:37: Cleaning SetupWatson key... 2017-09-17 13:00:37: Removing CorrelationVector registry value... 2017-09-17 13:00:37: Removing cleanup registry value... 2017-09-17 13:00:37: Creating path (with ACL): [C:\$WINDOWS.~BT]... 2017-09-17 13:00:38: Creating path: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 13:00:40: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] with command-line [/install /Media /InstallFile "F:\Sources\Install.esd" "/Compat" "ScanOnly" /MediaPath "F:"] in Session: [-1] 2017-09-17 13:00:40: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] [/install /Media /InstallFile "F:\Sources\Install.esd" "/Compat" "ScanOnly" /MediaPath "F:"] from []! 2017-09-17 13:00:40: Waiting for process events... 2017-09-17 13:04:02: Process exit code: [0x800704C7] 2017-09-17 13:04:02: LaunchProcessInSession: Error = 0x800704C7 2017-09-17 13:04:02: LaunchProcessInSession returned: [0x800704C7] 2017-09-17 13:04:02: Checking cleanup registry value... 2017-09-17 13:04:02: Checking SetupHost result value... 2017-09-17 13:04:02: Performing cleanup level: [0x1] 2017-09-17 13:04:02: Populating preservation paths... 2017-09-17 13:04:02: Acquiring privileges... 2017-09-17 13:04:02: Cleaning install folder... 2017-09-17 13:04:02: Cleaning folder: [C:\$WINDOWS.~BT\Boot]... 2017-09-17 13:04:02: Cleaning folder: [C:\$WINDOWS.~BT\Efi]... 2017-09-17 13:04:02: Protecting folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 13:04:02: Cleaning parent folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 13:04:02: Protecting folder: [C:\$WINDOWS.~BT\Sources\Diagnostics]... 2017-09-17 13:04:02: Cleaning folder: [C:\$WINDOWS.~BT\Sources\dlmanifests]... 2017-09-17 13:04:02: Cleaning folder: [C:\$WINDOWS.~BT\Sources\en-gb]... 2017-09-17 13:04:03: Cleaning folder: [C:\$WINDOWS.~BT\Sources\etwproviders]... 2017-09-17 13:04:03: Cleaning folder: [C:\$WINDOWS.~BT\Sources\hwcompat]... 2017-09-17 13:04:03: Cleaning folder: [C:\$WINDOWS.~BT\Sources\inf]... 2017-09-17 13:04:03: Cleaning folder: [C:\$WINDOWS.~BT\Sources\migration]... 2017-09-17 13:04:04: Protecting folder: [C:\$WINDOWS.~BT\Sources\Panther]... 2017-09-17 13:04:04: Cleaning folder: [C:\$WINDOWS.~BT\Sources\replacementmanifests]... 2017-09-17 13:04:04: Cleaning folder: [C:\$WINDOWS.~BT\Sources\sxs]... 2017-09-17 13:04:04: Cleaning MoSetup Volatile key... 2017-09-17 13:04:04: Cleaning MoSetup RegBackup key... 2017-09-17 13:04:04: Removing CorrelationVector registry value... 2017-09-17 13:04:04: Removing cleanup registry value... 2017-09-17 13:04:04: Path successfully cleaned! 2017-09-17 13:04:04: MainHr: Error = 0x800704C7 2017-09-17 13:04:04: wWinMain: Error = 0x800704C7 2017-09-17 17:42:02: CommandLine: [F:\Sources\SetupPrep.exe /Compat ScanOnly] 2017-09-17 17:42:02: Opening Box: [F:\Sources\SetupPrep.exe] 2017-09-17 17:42:02: Opening Box Result: [0x0] 2017-09-17 17:42:02: Deleting box result... 2017-09-17 17:42:02: ResumeMode: Not found. 2017-09-17 17:42:02: ResumeMode: [No] 2017-09-17 17:42:02: OsUninstallWarning: Execute file found [FALSE]. 2017-09-17 17:42:02: OsUninstallWarning: [No] 2017-09-17 17:42:02: Checking cleanup registry value... 2017-09-17 17:42:02: Checking SetupHost result value... 2017-09-17 17:42:02: SetupHost result missing! Forcing full cleanup... 2017-09-17 17:42:02: Performing cleanup level: [0x1] 2017-09-17 17:42:02: Populating preservation paths... 2017-09-17 17:42:02: Acquiring privileges... 2017-09-17 17:42:02: Cleaning install folder... 2017-09-17 17:42:02: Protecting folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 17:42:02: Cleaning parent folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 17:42:02: Protecting folder: [C:\$WINDOWS.~BT\Sources\Diagnostics]... 2017-09-17 17:42:02: Protecting folder: [C:\$WINDOWS.~BT\Sources\Panther]... 2017-09-17 17:42:02: Cleaning MoSetup Volatile key... 2017-09-17 17:42:02: Cleaning MoSetup RegBackup key... 2017-09-17 17:42:02: Removing CorrelationVector registry value... 2017-09-17 17:42:02: Removing cleanup registry value... 2017-09-17 17:42:02: Path successfully cleaned! 2017-09-17 17:42:02: Preserve working path: [No] 2017-09-17 17:42:02: Cleaning working dir... 2017-09-17 17:42:02: Attempting to close previous ETW session... 2017-09-17 17:42:02: Attempting to clean mounted registry hives... 2017-09-17 17:42:02: Attempting to clean mounted SafeOs image... 2017-09-17 17:42:02: Attempting to preserve existing logs... 2017-09-17 17:42:02: Cleaning path: [C:\Windows\Panther\NewOs]... 2017-09-17 17:42:02: Creating path: [C:\Windows\Panther\NewOs\Panther]... 2017-09-17 17:42:02: Copying [C:\$WINDOWS.~BT\Sources\Panther] -> [C:\Windows\Panther\NewOs\Panther]... 2017-09-17 17:42:03: Cleaning working path: [C:\$WINDOWS.~BT]... 2017-09-17 17:42:03: Cleaning alternate storage paths... 2017-09-17 17:42:03: Cleaning MoSetup Volatile key... 2017-09-17 17:42:03: Cleaning MoSetup RegBackup key... 2017-09-17 17:42:03: Cleaning SetupWatson key... 2017-09-17 17:42:03: Removing CorrelationVector registry value... 2017-09-17 17:42:03: Removing cleanup registry value... 2017-09-17 17:42:03: Creating path (with ACL): [C:\$WINDOWS.~BT]... 2017-09-17 17:42:03: Creating path: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 17:42:03: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] with command-line [/install /Media /InstallFile "F:\Sources\Install.esd" "/Compat" "ScanOnly" /MediaPath "F:"] in Session: [-1] 2017-09-17 17:42:03: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.exe] [/install /Media /InstallFile "F:\Sources\Install.esd" "/Compat" "ScanOnly" /MediaPath "F:"] from []! 2017-09-17 17:42:03: Waiting for process events... 2017-09-17 17:45:29: Process exit code: [0xC1900210] 2017-09-17 17:45:29: LaunchProcessInSession: Error = 0xC1900210 2017-09-17 17:45:29: LaunchProcessInSession returned: [0xC1900210] 2017-09-17 17:45:29: Checking cleanup registry value... 2017-09-17 17:45:30: Checking SetupHost result value... 2017-09-17 17:45:30: Performing cleanup level: [0x1] 2017-09-17 17:45:30: Populating preservation paths... 2017-09-17 17:45:30: Acquiring privileges... 2017-09-17 17:45:30: Cleaning install folder... 2017-09-17 17:45:30: Cleaning folder: [C:\$WINDOWS.~BT\Boot]... 2017-09-17 17:45:30: Cleaning folder: [C:\$WINDOWS.~BT\Efi]... 2017-09-17 17:45:30: Protecting folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 17:45:30: Cleaning parent folder: [C:\$WINDOWS.~BT\Sources]... 2017-09-17 17:45:30: Protecting folder: [C:\$WINDOWS.~BT\Sources\Diagnostics]... 2017-09-17 17:45:30: Cleaning folder: [C:\$WINDOWS.~BT\Sources\dlmanifests]... 2017-09-17 17:45:30: Cleaning folder: [C:\$WINDOWS.~BT\Sources\en-gb]... 2017-09-17 17:45:30: Cleaning folder: [C:\$WINDOWS.~BT\Sources\etwproviders]... 2017-09-17 17:45:31: Cleaning folder: [C:\$WINDOWS.~BT\Sources\hwcompat]... 2017-09-17 17:45:31: Cleaning folder: [C:\$WINDOWS.~BT\Sources\inf]... 2017-09-17 17:45:31: Cleaning folder: [C:\$WINDOWS.~BT\Sources\migration]... 2017-09-17 17:45:31: Protecting folder: [C:\$WINDOWS.~BT\Sources\Panther]... 2017-09-17 17:45:31: Cleaning folder: [C:\$WINDOWS.~BT\Sources\replacementmanifests]... 2017-09-17 17:45:32: Cleaning folder: [C:\$WINDOWS.~BT\Sources\sxs]... 2017-09-17 17:45:32: Cleaning MoSetup Volatile key... 2017-09-17 17:45:32: Cleaning MoSetup RegBackup key... 2017-09-17 17:45:32: Removing CorrelationVector registry value... 2017-09-17 17:45:32: Removing cleanup registry value... 2017-09-17 17:45:32: Path successfully cleaned! 2017-09-17 17:45:32: MainHr: Error = 0xC1900210 2017-09-17 17:45:32: wWinMain: Error = 0xC1900210 Edited September 17, 2017 by joddle Quote
Starbuck Posted September 18, 2017 Posted September 18, 2017 Hi joddle, Anyway cant make head nor tail of the results I'm not surprised. I'm having problems understanding it because of the inconsistencies. MainHr: Error = 0x800704C7 .... See Here and Here Then later you get..... MainHr: Error = 0xC1900210 .....indicates no errors found. When you run this ScanOnly execution, the results are returned via return codes from SETUP.EXE itself. Here are the possible values: No issues found: 0xC1900210 Compatibility issues found (hard block): 0xC1900208 Migration choice (auto upgrade) not available (probably the wrong SKU or architecture)· 0xC1900204 Does not meet system requirements for Windows 10: 0xC1900200 Insufficient free disk space: 0xC190020E Windows 10 Pre-Upgrade Validation using SETUP.EXE Quote Member of:UNITE
joddle Posted September 21, 2017 Author Posted September 21, 2017 Now unsure of how best to proceed - i.e whether to leave the PC as W7 or update to W10 1607 and leave it at that! Maybe wait also for next W10 build and see if they sort out the incompatibility error as apparently I am not the only one getting this issue. Quote
Starbuck Posted September 21, 2017 Posted September 21, 2017 I see your predicament joddle. Although Mainstream support has finished for Win7, you will still get Extended support until January 14, 2020. With Win10 creators edition, if an incompatible system is detected.... the update is meant to abort. But that's not to say that it always works. The big bugbare with Win10 is that you can't turn off the updates ..... so by installing an older version doesn't mean that it won't try and update again. If I was in your position, I'd probably opt for sticking with Win7 and saving myself the aggro. Quote Member of:UNITE
joddle Posted September 22, 2017 Author Posted September 22, 2017 I was thinking exactly that - no point going though it all again - may try again if a new build of w10 comes along in case the problem has been addressed by MS. Still can't work out why Creators works fine in the other two machines and not in this one though! The processors are different in all three but of the same generation so really only speed. Agreed the ram is a bit low but 4 GB should be OK - The only other difference is the bios version which I simply can't get to update - fails every time with "cant find files in memory" or something similar. (but what memory is it talking about???) I think there must be another issue with this pc as it always takes ages to boot and sticks with a little curser in the top left hand corner for ages before anything happens. No idea why though. Quote
Rustys Posted September 23, 2017 Posted September 23, 2017 The system that you are having the slow boot on is it the only one with MEBx? Quote "Confucius could give answer to that. Unfortunately, Confucius not here at moment.”
joddle Posted September 23, 2017 Author Posted September 23, 2017 Not sure what that means = they all have MEBx but this one did have a setting changed many years ago to stop it reacting every time is sensed the lan was active - all the tweak did was stop it reacting to the wake up - cant remember which setting was changed though/ Quote
Rustys Posted September 29, 2017 Posted September 29, 2017 I was asking if they all had MEBx or just the one that you were having issues with. Quote "Confucius could give answer to that. Unfortunately, Confucius not here at moment.”
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.