Win 7 to Win 10: Last Train to Format Station

Page 1 of 2 12 LastLast

  1. Posts : 8
    Win 7 Pro (64 bit)
       #1

    Win 7 to Win 10: Last Train to Format Station


    Hi, all-

    I've been fighting with my PC since July to upgrade from Windows 7 to Windows 10 and I am at my wit's end.
    I'm just about ready to perform a clean install of Windows 7 to see if that will upgrade to Windows 10, but I thought I would post one more time to see if anyone has a suggestion for getting around this error message I've found in SetupDiag:
    Error: 0x8007007B - 0x50015
    LogEntry: 2022-08-11 03:00:33, Error SP CMountWIM:oExecute: Failed to mount WIM file C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.

    For reference, these are my original posts from July:
    "Windows 10 installation has failed" Whut 2 dew?
    "Windows 10 installation has failed" - Windows 10 Forums

    Since those posts in July I have done everything suggested as well as a few other things:
    1.Downloaded the current Win 10 ISO & burned it to a DVD.
    2. Updated my BIOS & drivers.
    3. Manually uninstalled Norton 360.
    4. Run CHKDSK multiple times
    5. Run System File Checker multiple times.
    6. Tried upgrading using every permutation I can think of:
    DVD ISO with Network Connection OFF
    DVD ISO with Network Connection ON
    Run Setup.exe downloaded from Microsoft w/Network Connection OFF
    Run Setup.exe downloaded from Microsoft w/Network Connection ON

    To get the error messages I've been running the "Panther" folder thru SetupDiag on another PC that is running Win 10. The first time I did this, I found an error relating to the installation path that was easily fixed by changing a registry entry.

    This got my hopes up, but since then I've been stuck on the above error message.

    One thing that might be important: When I installed my current HD a few years ago I installed both Macrium and Acronis. I ended up using Acronis to clone my old HD to the new, larger HD, not sure why I used that over Macrium, but the first error message I received from SetupDiag referred to a missing wimmount.sys file in the Macrium folder, which was no longer on my system:
    DriverPath: C:\program files\macrium\reflect\wimmount.sys

    Changing the path fixed that issue.:
    C:\Windows\System32\drivers\wimmount.sys

    So...any ideas on how I can make this blasted thing work?

    If not, would you recommend cloning my current drive using Macrium over, say, just doing a straight copy of my current HD to an external HD?

    My inclination is to just copy my HD, format it, install Windows & use the copied files on my external HD as needed.

    Oh, current Windows version is:
    Version 6.1 (Build 7601: Service Pack 1)

    Thanks in advance for your advice!

    Best,

    Sam

    PS- For the record, I may take a quick look at gatherosstate.exe, before doing a clean install, if that ends up being my path.
      My Computer


  2. Posts : 15,585
    7 X64
       #2

    For the record, I may take a quick look at gatherosstate.exe, before doing a clean install, if that ends up being my path.
    That might end up being the way to do it.

    But first are you able to mount wim files in your current win7 ?
      My Computers


  3. Posts : 7,153
    Windows 7 HP 64
       #3

    Why don't you try first a Repair Install . It will reinstall Windows keeping your files and programs.

    Then, if you still want to downgrade to Win 10, use 7Zip to extract all files and folders from the Win 10 iso file to the a folder and then run Setup.exe

    Sometimes it just don't downgrade . I had a Sony Vaio that didn't. And on a Win 7 OEM (SLP license) there is no Win 7 key to retrieve. In this case use Clean Install Windows 10 Directly without having to Upgrade First. It will create some files to be used to activate Win 10 after a clean install
      My Computers


  4. Posts : 8
    Win 7 Pro (64 bit)
    Thread Starter
       #4

    SIW2 said:
    But first are you able to mount wim files in your current win7 ?
    @SIW2- Apologies for the delay in responding, the last few weeks have been busy, including welcoming a little one into the world!

    So, I'm in a little over my head re: mounting a wim file.

    I found the DISM command on my PC & I tried mounting the WIM file manually using various commands:
    Dism /Mount-Image /ImageFile:C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim /index:1 /MountDir:C:\test\offline

    Dism /Mount-Wim /ImageFile:C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim /index:1 /MountDir:C:\test\offline

    Dism /Mount-Wim /Image:C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim /index:1 /MountDir:C:\test\offline

    Dism /Mount-Wim /Online:C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim /index:1 /MountDir:C:\test\offline

    The above was a bit of experimenting, based on a Microsoft page that discusses mounting a WIM file in Windows 8.

    So, I'm hoping you can provide a little direction here:
    1. Should I be able to mount the WIM from the "$WINDOWS" folder?
    2. Is there an easy way to test whether or not I can mount a wim file?

    Best,

    Sam
    Last edited by Confuselled; 16 Sep 2022 at 02:51.
      My Computer


  5. Posts : 15,585
    7 X64
       #5

    Probably easiest to copy boot.wim from the installation media sources folder onto C:

    then try and mount c:\boot.wim

    you need to create an empty folder to mount it. You can give the folder any name you like, might as well call it MOUNT.

    create a folder called C:\MOUNT

    DISM /Mount-image /imagefile:c:\boot.wim /Index:1 /MountDir:c:\mount
      My Computers


  6. Posts : 7,153
    Windows 7 HP 64
       #6

    How much free drive space you have on C:?
    You should have at least 30G free space.

    Please post a whole window Disk Manager image of your drives. Don't forget to expand the columns so we can read them. Disk Management - Post a Screen Capture Image
    If you have a MiniTool or AOMEI Partition use it instead or Windows disk manager.
      My Computers


  7. Posts : 8
    Win 7 Pro (64 bit)
    Thread Starter
       #7

    SIW2 said:
    Probably easiest to copy boot.wim from the installation media sources folder onto C:
    then try and mount c:\boot.wim
    you need to create an empty folder to mount it. You can give the folder any name you like, might as well call it MOUNT.
    create a folder called C:\MOUNT
    DISM /Mount-image /imagefile:c:\boot.wim /Index:1 /MountDir:c:\mount
    @SIW2- I followed the steps you listed & received this error:
    Win 7 to Win 10: Last Train to Format Station-01.jpg

    These are the options listed for DISM:
    Win 7 to Win 10: Last Train to Format Station-02.jpg

    So I changed Mount-image to Mount-Wim & got this error:
    Win 7 to Win 10: Last Train to Format Station-03.jpg

    So, then I typed DISM /Mount-Wim /? to see this:
    Win 7 to Win 10: Last Train to Format Station-04.jpg

    Based on that, I tried running their sample command:
    Win 7 to Win 10: Last Train to Format Station-05.jpg

    Now, I am really tired, but I'm pretty sure I typed all that in correctly.

    I'm more Confuselled than ever.

    Did I go wrong with the /Mount-Wim command?

    Should I just buy a Mac?

    Any thoughts?

    Best,

    Sam
    Last edited by Confuselled; 17 Sep 2022 at 01:54.
      My Computer


  8. Posts : 15,585
    7 X64
       #8

    Did I go wrong with the /Mount-Wim command?
    you were correct.

    I forgot the commands for win7 are different and gave you the commands for newer versions of dism by mistake.

    DISM.exe /Mount-Wim /WimFile:C:\boot.wim /index:1 /MountDir:C:\mount

    should work if c:\boot.wim and c:\mount exist.
      My Computers


  9. Posts : 8
    Win 7 Pro (64 bit)
    Thread Starter
       #9

    SIW2 said:
    you were correct.
    I forgot the commands for win7 are different and gave you the commands for newer versions of dism by mistake.
    DISM.exe /Mount-Wim /WimFile:C:\boot.wim /index:1 /MountDir:C:\mount
    should work if c:\boot.wim and c:\mount exist.
    @SIW2- OK, I ran the command and now things are getting interesting or weird, or maybe both.

    I received this error message:
    Win 7 to Win 10: Last Train to Format Station-.jpg

    I opened the log file and it appears the command is looking for my "D:" drive:
    2022-09-17 23:45:31, Info DISM PID=3208 Scratch directory set to 'C:\Users\WINDOW~1\AppData\Local\Temp\'. - CDISMManager:ut_ScratchDir
    2022-09-17 23:45:31, Info DISM PID=3208 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Manager: PID=3208 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM.EXE:
    2022-09-17 23:45:31, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2022-09-17 23:45:31, Info DISM DISM.EXE:
    2022-09-17 23:45:31, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=8
    2022-09-17 23:45:31, Info DISM DISM.EXE: Executing command line: DISM.exe /Mount-Wim /WimFile:C:\boot.wim /index:1 /MountDir:c:\mount
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2022-09-17 23:45:31, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2022-09-17 23:45:31, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
    2022-09-17 23:45:31, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2022-09-17 23:45:31, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
    2022-09-17 23:45:31, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2022-09-17 23:45:31, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2022-09-17 23:45:31, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Getting Provider WimManager - CDISMProviderStore::GetProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2022-09-17 23:45:31, Error DISM DISM WIM Provider: PID=3208 Failed to mount the image. - CWimImageInfo::Mount(hr:0x8007007b)
    2022-09-17 23:45:31, Error DISM DISM WIM Provider: PID=3208 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x8007007b)
    2022-09-17 23:45:31, Error DISM DISM WIM Provider: PID=3208 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x8007007b)
    2022-09-17 23:45:31, Error DISM DISM WIM Provider: PID=3208 Error executing command - CWimManager::InternalExecuteCmd(hr:0x8007007b)
    2022-09-17 23:45:31, Error DISM DISM WIM Provider: PID=3208 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x8007007b)
    2022-09-17 23:45:31, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2022-09-17 23:45:31, Info DISM DISM.EXE:
    2022-09-17 23:45:31, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2022-09-17 23:45:31, Info DISM DISM.EXE:
    2022-09-17 23:45:31, Info DISM DISM Image Session: PID=3208 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2022-09-17 23:45:31, Info DISM DISM Provider Store: PID=3208 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    I do have a second hard drive in my PC, it's the original 2Tb hard drive that I replaced with the current 4Tb hard drive, but I unplugged it for the Win 10 upgrade. However, I think this was after a few attempts at running the Windows 10 upgrade.

    Is it possible that my old hard drive has somehow been linked to the upgrade process?

    For reference, here is a screenshot of my existing hard drive & the DVD containing the ISO:
    Win 7 to Win 10: Last Train to Format Station-b.jpg

    Do you have any thoughts on what this mad PC of mine is doing?

    Best,

    Sam
    "Curiouser and curiouser!"- Alice in Wonderland
      My Computer


  10. Posts : 15,585
    7 X64
       #10

    Have you used any tools such as waik ?

    Might have happened during creation of macrium recovery media.
      My Computers


 
Page 1 of 2 12 LastLast

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

Designer Media Ltd
All times are GMT -5. The time now is 17:05.
Find Us