Windows will only load "After" pressing the ReSet button ?

Page 1 of 2 12 LastLast

  1. Posts : 77
    Windows 10 Pro. Build 19045.4291 Version 22H2
       #1

    Windows will only load "After" pressing the ReSet button ?


    I recently cloned a fairly fresh install of W10 Pro 22H2 OS Build 19045.3448 to an old mechanical HDD for backup purposes.
    This was done with an old version of Paragon Hard Disk Manager.
    This Paragon CD has now been put through the shredder, as I found that I have a spare version of Acronis 2016.
    I have not tried Acronis on this new install yet.


    If I press the start button - the Computer hangs at the Logo Screen/ Press F2 etc.
    If I press the "ReSet" button, windows will then load fully.

    Once at my Desktop, if I press the restart button, the Computer hangs at the LogoScreen/ Press F2 etc.
    If I press the "ReSet" button, windows will then load fully.

    Once at my Desktop, if I send the computer to sleep, it will awaken as normal when any key is pressed.

    All of the above happens with my original SSD or my cloned mechanical HDD.Windows will only load "After" pressing the ReSet button ?-b85m.png



    UPDATE:::
    When I initially installed windows I made a clone using a Docking Station/Duplicator. This worked just fine, but it takes along time. Using Clone software is much quicker, so that's why I used it.

    But, this bare bones windows SSD that has not had any contact with cloning software, is having the exact same problems as those above ?

    Has something in the BIOS gone wonky ?

    Currently doing another Dock Station clone just in case.
    Last edited by FredM8; 14 Sep 2023 at 01:10.
      My Computer


  2. Posts : 43,197
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, your disk shows a single partition. MBR and UEFI installations normally consist of up to 4- not 1.
    Could you explain how how got to that please?

    History: (so often not given by posters):
    When was the last time your PC booted normally?
    What happened before this changed?
    Was cloning the disk the only thing that happened before this started?

    Your MOBO seems to be relatively old - perhaps from 2014. CMOS battery perhaps?

    Otherwise I would have said: start with the simple things: you can try Windows Startup Repair

    - from the excellent huge searchable Tutorials section (do feel free to have a look):
    Run Startup Repair in Windows 10
    Once again, blue text in tutorials is usually a link.

    If necessary try Macrium Reflect's Fix Boot utility on its boot disk .

    Install a free copy of MR, create its boot disk, boot PC from that, use utility.

    Note: Macrium R is generally preferred and recommended for disk imaging etc rather than Acronis; the free version is available but is no longer developed. There are others free and given away periodically (Aomei Backupper, O&O Diskimage...).
    Last edited by dalchina; 14 Sep 2023 at 07:59.
      My Computers


  3. Posts : 4,631
    several
       #3

    disk shows a single partition
    It is quite common.

    the Computer hangs at the Logo Screen/ Press F2 etc.
    presumably that is the bios logo.
      My Computer


  4. Posts : 77
    Windows 10 Pro. Build 19045.4291 Version 22H2
    Thread Starter
       #4

    dalchina said:
    Hi, your disk shows a single partition. MBR and UEFI installations normally consist of up to 4- not 1.
    Could you explain how how got to that please?

    History: (so often not given by posters):
    When was the last time your PC booted normally?
    What happened before this changed?
    Was the cloning the disk the only thing that happened before this started?

    Your MOBO seems to be relatively old - perhaps from 2014. CMOS battery perhaps?

    Otherwise I would have said: start with the simple things: you can try Windows Startup Repair

    - from the excellent huge searchable Tutorials section (do feel free to have a look):
    Run Startup Repair in Windows 10
    Once again, blue text in tutorials is usually a link.

    If necessary try Macrium Reflect's Fix Boot utility on its boot disk .

    Install a free copy of MR, create its boot disk, boot PC from that, use utility.

    Note: Macrium R is generally preferred and recommended for disk imaging etc rather than Acronis; the free version is available but is no longer developed. There are others free and given away periodically (Aomei Backupper, O&O Diskimage...).
    It is an old but unused MOBO, and the battery was replaced before the build.

    As described above, things went wrong after contact with an old version of Paragon HD Manager to make a software clone as it is in theory much quicker than a Docking station clone.

    But now I find that a original Dock clone that has had no contact with cloning software is having the same start up/loading problem.

    - - - Updated - - -

    SIW2 said:
    It is quite common.



    presumably that is the bios logo.
    Yes, that it.
      My Computer


  5. Posts : 43,197
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5

    And thank you for your reply.

    Please then try what I suggested.
      My Computers


  6. Posts : 77
    Windows 10 Pro. Build 19045.4291 Version 22H2
    Thread Starter
       #6

    dalchina said:
    And thank you for your reply.

    Please then try what I suggested.
    Given what I have just tried with a bare bones clone made with a Docking station, would windows repair have any effect ?

    It's starting to look like a BIOS issue.

    What do you think ?

    The OS is on one partition because that is how Windows installed it.
      My Computer


  7. Posts : 43,197
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #7

    Normally MBR systems are 3 partitions, UEFI 4, when clean installed in the usual way.

    One of those partitions is a Recovery partition, for example.

    It can be done differently.

    It certainly isn't clear why simply cloning a disk would have an adverse effect.
      My Computers


  8. Posts : 77
    Windows 10 Pro. Build 19045.4291 Version 22H2
    Thread Starter
       #8

    dalchina said:
    Normally MBR systems are 3 partitions, UEFI 4, when clean installed in the usual way.

    One of those partitions is a Recovery partition, for example.

    It can be done differently.

    It certainly isn't clear why simply cloning a disk would have an adverse effect.

    I can't work it out either.
    In the BIOS I have set everything to "default" and the SSD that I am using now has been nowhere any cloning software.
    This little problem remains ?

    I have to press the Reset button every time ?
      My Computer


  9. Posts : 43,197
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #9

    I would still like to see the result of running Startup Repair and MR Fix Boot.

    If these fail, there may be useful info.

    And as I said, only having C: is unusual.

    Is yours a MBR (legacy) installation?

    Note that if the other partitions have somehow 'disappeared', provided your C: partition is intact, it would still be possible to recover.

    You might also try a 3rd party partition manager e.g. Minitool Partition Wizard and see what that shows.
      My Computers


  10. Posts : 77
    Windows 10 Pro. Build 19045.4291 Version 22H2
    Thread Starter
       #10

    dalchina said:
    I would still like to see the result of running Startup Repair and MR Fix Boot.

    If these fail, there may be useful info.

    And as I said, only having C: is unusual.

    Is yours a MBR (legacy) installation?

    Note that if the other partitions have somehow 'disappeared', provided your C: partition is intact, it would still be possible to recover.

    You might also try a 3rd party partition manager e.g. Minitool Partition Wizard and see what that shows.
    I tried the Windows repair route with my installation CD but Windows was unable to repair.

    As it has been such a new install, I decided to do a completely new fresh install.
    As usual, I disconnected all usb stuff first and installed W10 Pro on a fresh SSD. After the basic new install everything started and behaved as it should do.

    Just out of curiosity, I connected the SSD with the problem installation on it, and hey presto it all went just right !!

    So, it looks as though there has been some sort of conflict with one or more of my peripherals, that only became apparent after the installation of Paragon, or were caused by a conflict with Paragon.

    Who knows !



    I will keep a closer watch as I add things in the future.
    But effective cloning software is my first port of call.
    Must dig out my spare Acronis key for this MOBO.

    Like I said it is an old MOBO but never used.
    ASUS B85M-G it still does a good job and will suite my purpose.

    Thanks to all !!
      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 05:20.
Find Us




Windows 10 Forums