BrianDrab
Emeritus
Yes go on with the FRST one.
[SOLVED] [Win10v1511Build10586Ent x64] 0x8024200D error trying to install v1607
- Thread starter buybuy
- Start date
Fix result of Farbar Recovery Scan Tool (x64) Version: 27-04-2017
Ran by Loredana (03-05-2017 20:39:07) Run:8
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
cmd: reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s
*****************
========= reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s =========
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2
Mount Version REG_DWORD 0x10001
Image time high REG_DWORD 0x1d24376
Image time low REG_DWORD 0x51f66c59
Status REG_DWORD 0x2
Mount Path REG_SZ C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
WIM Path REG_SZ C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim
Image Index REG_DWORD 0x1
FileCount REG_DWORD 0x4303
Mount path high REG_DWORD 0x7c0000
Mount path low REG_DWORD 0x3d49
========= End of CMD: =========
==== End of Fixlog 20:39:07 ====
Ran by Loredana (03-05-2017 20:39:07) Run:8
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
cmd: reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s
*****************
========= reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s =========
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2
Mount Version REG_DWORD 0x10001
Image time high REG_DWORD 0x1d24376
Image time low REG_DWORD 0x51f66c59
Status REG_DWORD 0x2
Mount Path REG_SZ C:\$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount
WIM Path REG_SZ C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim
Image Index REG_DWORD 0x1
FileCount REG_DWORD 0x4303
Mount path high REG_DWORD 0x7c0000
Mount path low REG_DWORD 0x3d49
========= End of CMD: =========
==== End of Fixlog 20:39:07 ====
As I did before, I have to execute this script in FRST?
Fixlist.txt content:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2]
CreateRestorePoint:
C:\$WINDOWS.~BT
C:\windows\SoftwareDistribution
EmptyTemp:
Fixlist.txt content:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2]
CreateRestorePoint:
C:\$WINDOWS.~BT
C:\windows\SoftwareDistribution
EmptyTemp:
Sorry for adding myself to this thread, I hope this doesn't break any rules, but I have the exact same problem of buybuy (Windows is stuck to version 1511 build 10586.83 since february). I'm quite an advanced user and I've tried everything to no avail. The only difference (by the way I'm italian too) is that my version of Windows is the pro one and not the enterprise and that it has been upgraded from Windows 8.1. I suspect that the problem may be related to that. Is your version of Windows a fresh install or has it been upgraded from 8.1 too? Sorry again for interrupting but I'm monitoring this thread to check if you will, hopefully, find a solution.
Thank you.
Thank you.
BrianDrab
Emeritus
buybuy - Actually, run the attach script through instead.
Gastel71 - Thanks for the information. Always great to have extra information to go on.
Gastel71 - Thanks for the information. Always great to have extra information to go on.
Gastel71 - I did fresh installation :huh:
BrianDrab - Log:
Fix result of Farbar Recovery Scan Tool (x64) Version: 03-05-2017 01
Ran by Loredana (03-05-2017 23:44:09) Run:9
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2]
*****************
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2 => key removed successfully
==== End of Fixlog 23:44:09 ====
BrianDrab - Log:
Fix result of Farbar Recovery Scan Tool (x64) Version: 03-05-2017 01
Ran by Loredana (03-05-2017 23:44:09) Run:9
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2]
*****************
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\953954c4-c726-40a2-a794-75ac17a581c2 => key removed successfully
==== End of Fixlog 23:44:09 ====
BrianDrab
Emeritus
Try updating again please.
I avoided to adopt the most drastic solution (format and install again), also because I have this problem replicated on 10 PC (I used Acronis True Image to clone installation on a stock of PC).
But I'm afraid that you guided me to all the possible workaround to solve the problem and now the last one is to format and install again.
Don't you think so? Is there anithing else that we can do?
But I'm afraid that you guided me to all the possible workaround to solve the problem and now the last one is to format and install again.
Don't you think so? Is there anithing else that we can do?
BrianDrab
Emeritus
I can try a couple more things but ultimately it's up to you. Just let me know.
BrianDrab
Emeritus
Please do the following.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the upgrade like you have in the past.
3. Stop Process Monitor as soon as the Upgrade fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the upgrade like you have in the past.
3. Stop Process Monitor as soon as the Upgrade fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
I had to start monitoring from " 85% installation progress " because otherwise I receive error "Memory insufficient".
At this link you can find logs:
WeTransfer
At this link you can find logs:
WeTransfer
BrianDrab
Emeritus
No problem. As long as the process monitor was running during the time the error came up. I assume that's the case?
BrianDrab
Emeritus
Please also zip/attach the following file.
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
BrianDrab
Emeritus
Please do the following.
FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Fix result of Farbar Recovery Scan Tool (x64) Version: 07-05-2017
Ran by Loredana (08-05-2017 10:13:01) Run:10
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
S3 cpuz140; C:\Users\Loredana\AppData\Local\Temp\cpuz140\cpuz140_x64.sys [43840 2017-04-26] (CPUID) <==== ATTENTION
EmptyTemp:
*****************
HKLM\System\CurrentControlSet\Services\cpuz140 => key removed successfully
cpuz140 => service removed successfully
=========== EmptyTemp: ==========
BITS transfer queue => 32768 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 5293752 B
Java, Flash, Steam htmlcache => 0 B
Windows/system/drivers => 90465 B
Edge => 3750796 B
Chrome => 93675186 B
Firefox => 0 B
Opera => 0 B
Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 128 B
systemprofile32 => 128 B
LocalService => 7374 B
NetworkService => 12318 B
Ripartiz Informatica => 0 B
Loredana => 8833101 B
RecycleBin => 0 B
EmptyTemp: => 106.5 MB temporary data Removed.
================================
The system needed a reboot.
==== End of Fixlog 10:13:04 ====
Ran by Loredana (08-05-2017 10:13:01) Run:10
Running from C:\Users\Loredana\Desktop
Loaded Profiles: Loredana (Available Profiles: Ripartiz Informatica & Loredana)
Boot Mode: Normal
==============================================
fixlist content:
*****************
S3 cpuz140; C:\Users\Loredana\AppData\Local\Temp\cpuz140\cpuz140_x64.sys [43840 2017-04-26] (CPUID) <==== ATTENTION
EmptyTemp:
*****************
HKLM\System\CurrentControlSet\Services\cpuz140 => key removed successfully
cpuz140 => service removed successfully
=========== EmptyTemp: ==========
BITS transfer queue => 32768 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 5293752 B
Java, Flash, Steam htmlcache => 0 B
Windows/system/drivers => 90465 B
Edge => 3750796 B
Chrome => 93675186 B
Firefox => 0 B
Opera => 0 B
Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 128 B
systemprofile32 => 128 B
LocalService => 7374 B
NetworkService => 12318 B
Ripartiz Informatica => 0 B
Loredana => 8833101 B
RecycleBin => 0 B
EmptyTemp: => 106.5 MB temporary data Removed.
================================
The system needed a reboot.
==== End of Fixlog 10:13:04 ====
BrianDrab
Emeritus
Please do the following again.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the upgrade like you have in the past.
3. Stop Process Monitor as soon as the Upgrade fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the upgrade like you have in the past.
3. Stop Process Monitor as soon as the Upgrade fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
Has Sysnative Forums helped you? Please consider donating to help us support the site!