Cannot clone or image failing drive - how to proceed?

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10 Pro
       #1

    Cannot clone or image failing drive - how to proceed?


    I have a Dell XPS studio 9100 (close to 10 years old!). This afternoon I got a bluescreen of death.
    I rebooted and was greeted with a bios screen showing the SMART status of the 1.5TB boot drive is bad.
    I had to disabled SMART checking in the BIOS in order to be able to boot the machine again and am trying to proceed with a backup. I have file history and EaseUS file level backups but no recent images which I can restore so I have been trying to clone the drive to avoid having to re-install a lot of software.

    A clone operation using EaseUS failed with no explanation.
    I tried Macrium Reflect which at least showed me what it was doing before it too failed. There are three partitions on the drive: a small OEM utilities partition, a 16GB Recovery Partition and the main C: Partition. The first two partitions cloned correctly but the clone operation on the main drive fails with the suggestion to run
    Code:
    chkdsk /r
    chkdsk /r hangs at 11%. I stopped it after four hours...

    Following some other suggestions I ran Disk Cleanup (oddly it showed 0 bytes to recover). Then, using elevated PowerShell I ran:

    Code:
    sfc /scannow
    That fails at 37% complete with the error: Windows Resource Protection could not perform the requested operation.

    So I am wondering what the best plan is.

    1 - keep trying to repair the damaged drive so that it can be cloned or imaged.
    2 - find another way to clone the damaged drive without repairing it first (given that it boots and works just fine [for now at least]).
    3 - fresh install of windows on a new drive and then migrate.

    Any thoughts on the problem, suggestions as to which approach to take and how to execute it would be greatly appreciated!

    Many thanks,

    b
      My Computer


  2. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    1) There are log collectors used in another forum.
    2) Run both DM and BETA log collectors and post zips into this thread
    BSOD - Posting Instructions - Windows 10 Forums

    3) Open administrative command prompt and type or copy and paste:
    4) dism /online /cleanup-image /scanhealth
    5) dism /online /cleanup-image /restorehealth
    6) sfc /scannow
    7) chkdsk /scan
    8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    9) When using chkdsk /f or chkdsk /r it should require a reboot and then rise to a low level in the teens until it has completed.

    After posting the above results (1 -9)
    Open administrative command prompt and type or copy and paste: chkdsk /r /v c:

    This command may take many hours so plan to run overnight.

    C:\WINDOWS\system32>chkdsk /r /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    10) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a one drive, drop box, or google drive share link into the thread

    Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials

    11) Run the Dell diagnostics: Full test > post an image of the results into the thread
    Support for Studio XPS 9100 | Diagnostics | Dell US


    12) Run HD Tune (free edition):
    https://www.hdtune.com/
    Post images of the results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    13) Run Sea Tools for Windows
    a) long generic scan > post an image of the results into the thead

    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows | Seagate Support

    14) Find a flash drive that you can format ( > or = 8 GB)

    15) Create a bootable Windows 10 iso:
    Download Windows 10
    Download Windows 10 ISO File | Tutorials

    16) A backup plan is an in place upgrade repair if scannow cannot be fixed
    Repair Install Windows 10 with an In-place Upgrade | Tutorials
      My Computer


  3. Posts : 6
    Windows 10 Pro
    Thread Starter
       #3

    Thanks for the detailed reply zbook.

    1) I downloaded DM log collector to the boot drive and ran it. After UAC authorization a cmd windows opens and then closes again without asking for a destination for the log info. Ran as admin with same result.
    2) Extracting the zip file of the v2-beta to the HD failed so I put it on a USB stick and ran it. It failed with the following errors in the cmd window:

    Code:
    Beta16 - 9/15/18
    New-Item : The file or directory is corrupted and unreadable.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:155 char:2
    +     New-Item -ItemType Directory -Path $EventLogs | Out-Null
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (C:\Users\rhubar...-54)\Event Logs:S
       tring) [New-Item], IOException
        + FullyQualifiedErrorId : CreateDirectoryIOError,Microsoft.PowerShell.Comm
       ands.NewItemCommand
    
    New-Item : The file or directory is corrupted and unreadable.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:156 char:2
    +     New-Item -ItemType Directory -Path $PowerReports | Out-Null
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (C:\Users\rhubar...)\Power Reports:S
       tring) [New-Item], IOException
        + FullyQualifiedErrorId : CreateDirectoryIOError,Microsoft.PowerShell.Comm
       ands.NewItemCommand
    
    Generating system information report, this may take a while...
    Downloading autorunsc...
    WARNING: Failed to download autorunsc. Skipping...
    Launching elevated script...
    Running DirectX diagnostics...
    Exporting Application event Log...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\Event Logs\application-events.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:270 char:116
    + ... e) <= 2592000000]]]" /f:text | Out-File -FilePath $AppEvents 2> $null
    +                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Exporting System event log...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\Event Logs\system-events.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:273 char:111
    + ... <= 2592000000]]]" /f:text | Out-File -FilePath $SystemEvents 2> $null
    +                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Exporting Kernel PnP event log...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\Event Logs\pnp-events.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:276 char:147
    + ... e) <= 2592000000]]]" /f:text | Out-File -FilePath $PnPEvents 2> $null
    +                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\os-details.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:279 char:181
    + ... InstallDate, BootDevice, SystemDevice | Out-File -FilePath $OSDetails
    +                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Gathering device driver information...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\driver-versions.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:284 char:150
    + ... iceName | Format-Table -AutoSize | Out-File -FilePath $DriverVersions
    +                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Checking power settings...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\Power Reports\power-plan.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:288 char:33
    + &$PowerCfgPath /list 2> $null | Out-File -FilePath $PowerPlan
    +                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Getting hardware information...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\ram.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:292 char:18
    + Get-MemoryInfo | Out-File -FilePath $RAM
    +                  ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\cpu.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:298 char:97
    + ... t-Object $ProcessorAttributes | Format-List | Out-File -FilePath $CPU
    +                                                   ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\motherboard.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:301 char:38
    + ... utput "Motherboard Details" | Out-File -Append -FilePath $Motherboard
    +                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\motherboard.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:303 char:97
    + ... ardAttributes | Format-List | Out-File -Append -FilePath $Motherboard
    +                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\motherboard.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:306 char:36
    + ... -Output "UEFI/BIOS Details" | Out-File -Append -FilePath $Motherboard
    +                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\motherboard.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:308 char:87
    + ... iosAttributes | Format-List | Out-File -Append -FilePath $Motherboard
    +                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\gpu.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:314 char:97
    + ...  Select-Object $GpuAttributes | Format-List | Out-File -FilePath $GPU
    +                                                   ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Listing installed software...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:322 char:52
    + ... Name | Format-Table -AutoSize | Out-File -FilePath $InstalledSoftware
    +                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:326 char:35
    + ... put "32-bit Software" | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:327 char:288
    + ... ormat-Table -AutoSize | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:330 char:41
    + ... er-specific Software" | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:331 char:167
    + ... ormat-Table -AutoSize | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:333 char:47
    + ... d Windows Components" | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\installed-software.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:334 char:226
    + ... ormat-Table -AutoSize | Out-File -Append -FilePath $InstalledSoftware
    +                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Listing installed Windows updates...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\windows-updates.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:338 char:165
    + ... otFixID | Format-Table -AutoSize | Out-File -FilePath $WindowsUpdates
    +                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Finding network information...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\network-info.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:342 char:73
    + ... ll 2> $null | Select-Object -Skip 1 | Out-File -FilePath $NetworkInfo
    +                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\network-info.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:343 char:21
    + &$RoutePath print | Out-File -Append -FilePath $NetworkInfo 2> $null
    +                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Examining hosts file...
    Out-File : Could not find a part of the path 'C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\hosts.txt'.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:350 char:73
    + ... lect-String '(127.0.0.1)|(0.0.0.0)' | Out-File -FilePath $HostsReport
    +                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
        + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand
    
    Creating Windows license report...
    WARNING: C:\Users\rhubarb\AppData\Local\Temp\genuine.xml does not exist.
    Wait-Process : Cannot validate argument on parameter 'DestinationPath'. The " Test-Path -Path (Split-Path -Path $_ -Parent) " validation script for the argument with value "C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\dxdiag.txt" did not return a result of True. Determine why the validation script failed, and then try the command again.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:388 char:112
    + ... diag.exe" -TimeoutSeconds $DxDiagTimeout -DestinationPath $DxDiagFile
    +                                                               ~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Wait-Process], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationError,Wait-Process
    
    Wait-Process : Cannot validate argument on parameter 'DestinationPath'. The " Test-Path -Path (Split-Path -Path $_ -Parent) " validation script for the argument with value "C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\msinfo32.nfo" did not return a result of True. Determine why the validation script failed, and then try the command again.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:400 char:118
    + ... 32.exe" -TimeoutSeconds $MsInfo32Timeout -DestinationPath $SystemInfo
    +                                                               ~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Wait-Process], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationError,Wait-Process
    
    WARNING: C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)\msinfo32.nfo not
     found, msinfo32 may have crashed or was canceled by the user.
    Waiting for elevated script to finish...
    Killed elevated script due to 150 second timeout.
    Move-Item : Cannot create a file when that file already exists.
    At E:\DM log collectors\log collector v2-beta16\resources\main.ps1:432 char:5
    +     Move-Item -Path $FileHashes -Destination $Path
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (C:\Users\rhubar...ocal\hashes.txt:FileInfo) [Move-Item], IOException
        + FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand
    
    Compressing folder...
    WARNING: Failed to compress the folder.
    
    
    WARNING: Compression failed!
    
    
    Output location: C:\Users\rhubarb\Desktop\NOESIS-(2018-12-30_10-13-54)
    
    
    Press Enter to exit:
    and in the admin Powershell:

    Code:
    E:\DM log collectors\log collector v2-beta16\resources\elevated.ps1 : Cannot dot-source this command because it was
    defined in a different language mode. To invoke this command without importing its contents, omit the '.' operator.
        + CategoryInfo          : InvalidOperation: (:) [elevated.ps1], NotSupportedException
        + FullyQualifiedErrorId : DotSourceNotSupported,elevated.ps1

    There is a also a System Information error window: The system cannot find the path specified.

    I also tried to copy the log collector to the desktop and get Error 0x80070570: The file or directory is corrupted and unreadable. I'm going to reboot and see if the system will repair the file hierarchy before proceeding.
      My Computer


  4. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    1) When available please post results for steps 3 to 8.

    2) Boot into safe mode:
    Boot into Safe Mode on Windows 10 | Tutorials

    3) Run sfc /scannow in safe mode 3 times

    4) Open administrative command prompt and type or copy and paste:
    systeminfo
    When this has completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    5) In the left lower corner type: dxdiag > click on dxdiag run command > when the dxdiag diagnostic tool opens click on next to open each tab > click save all information > save as txt file to the desktop > post a share link into the thread

    6) In the left lower corner type: msinfo32 > save as NFO > post a share link into the thread

    7) Find a flash drive that you can format (> or = 4 GB)

    8) On a working computer create a Kyhi boot rescue flash drive:
    Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
      My Computer


  5. Posts : 6
    Windows 10 Pro
    Thread Starter
       #5

    Bad to worse. The NTFS file system is now damaged and automatic recovery failed to fix it.
    I am in the process of liberating a flash drive to setup a Kyhi rescue drive.
    I was going to start with Minitool to try and repair the partition.
      My Computer


  6. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Copy and paste any important files to another drive or to the cloud using Kyhi boot rescue.
      My Computer


  7. Posts : 8,100
    windows 10
       #7

    Did you clone a disk with has sectors the will be written to the new drive and cant be reveresed you also dont know what files are corupt
      My Computer


  8. Posts : 6
    Windows 10 Pro
    Thread Starter
       #8

    It took about five hours, but MiniTool Partition repaired the damage to the NTFS file system well enough for me to be able to use Samsung Data Migration to clone the system to a new SSD. I shall be taking a hammer to the old drive.

    Many many thanks for your help!
      My Computer


  9. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    Nice work.
    Which version of mini tool (free or pay)
    What menu steps?
      My Computer


  10. Posts : 6
    Windows 10 Pro
    Thread Starter
       #10

    I burnt the Kyhi ISO to a USB, booted from that and used the free version of the Minitool Partition from there.
    I selected the damaged partition and ran "Repair File System".
    The scan found damage to the file table and rebuilt it.

    After repair, the drive booted again and I copied data manually to another HDD before attempting to clone it with Samsung Data Migration. SDM doesn't show any details of what it is going on during the transfer, so it is not clear whether there was any corrupt data that was transferred or ignored.
    Now I'm testing the machine and all of the transferred software - so far so good.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:48.
Find Us




Windows 10 Forums