The system always makes full boot on startup. I tried to restore to a saved point, but it says it could not retrieve saved information.
I feel the file system could be broken. How can I fix it? I used checkdisk but it found no errors.
Your system specs say you are on Windows 8.1.
Is that correct? It might help if you filled out more details in your specs.
System Restore is not highly reliable in any case. You would be better off with an image backup.
What exactly do you mean by "the file system could be broken"?
Do you have any particular reason to think you have hard drive issues?
Other than System Restore, can you describe your complaint more clearly?
Yes, but on Win8 forum there is no reply.
It seems to me that the system before full boot cannot access some NTFS features such as stored old file versions etc. The restore point is created without an error after the system boots but it says it cannot extract the necessary info when trying to restore the system.
I think something got broken when I started a very old disk manager utility just for curiosity. That disk manager clearly did not know about modern versions of NTFS. It said something like "updating disk info..." upon start. And after that all those issues began.
Hello @Anixx,
I cannot suggest any solution for your issue but if I were you, I would follow this:
First, I'd create a backup of my system to an external hard disk using Macrium Reflect Free edition:
Backup and Restore with Macrium Reflect
Then, I'd try to upgrade to Windows 10 (keeping my apps) which is still for free:
Or, I'd perform a Win10 clean install (deleting Win8 installation):
If anything goes wrong, I'd restore my backup image, searching for a fixing.
I think, there is no reason to stay on Win8 anymore unless there is a very serious reason.
Note: Never trust Windows System Restore!
Last edited by HeM; 05 Nov 2019 at 01:26.
Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.
Please type below command into Command Prompt and press Enter key.
Following command will fixes errors on the disk and locates bad sectors and recovers readable information.
Code:Chkdsk D: /r
Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.
Please type below command into Command Prompt and press Enter key.
The following command scans integrity of all protected Windows system files and repairs files with problems when possible.
Code:Sfc /Scannow /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows
Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
No, I will not switch to Windows 10 because of the following reasons:
1. Windows 10 taskbar is broken in Windows Classic theme I use
2. In some builds of Windows 10 the File Explorer is also broken in Windows Classic theme, and there is no guarantee it will not be broken in some later release.
3. Windows Explorer context menus do not appear in Windows Classic theme
4. Windows 10 requires reinstall each 6 months and this computer is too critical for me to do it. I even cannot risk with one reinstall.
5. After each 6-month Windows 10 update I would have to re-do all the system customizations I made.
6. I use third-party customization software such as Classic Shell and 7+ Taskbar Tweaker, there is no guaratee they will continue to work with later Windows 10 builds.
7. I like consistent user interface and do not like the Metro interface, I dislike when in File Explorer the context menu is Metro-based while in other programs it is not. I dislike when Calculator looks unlike other programs. I like consistent user interface.
- - - Updated - - -
I have already run chckdisk with various options, including /r /f. It did not find any errors.
I also did sfc /scannow.
I also tried to do boot repair from the boot menu, but it said it failed. I also tried to fallback to a restore point from the boot menu, again, with no success.
I really and absolutely understand you. I had about the same opinion for Win10 especially with that Windows As A Service "fruit".
I had decided to stay on 1511 version for a few years, disabling automatic updates and many other things and services. The result after 2 years? A gradually declining system which only for manually security updates was taking me even a whole day, restarting, Dism-ing, restoring etc.
Two years later, I decided to try just for a few days, current build (1703) letting Windows work as MS wanted, leaving aside any objections I had and passing on all that was necessary for my security and privacy.
The result? I was impressed with the stability, reliability and ease of dealing with any failure (really, not many) that may have occurred.
Since those days I've realized, there is no any reason (especially if it's about an app) for me to spend my life resisting to something new that I cannot understand the reason of its existence.
Now, I follow Win10, bringing system to my steps and I think, that's really life. I don't want to stay in my "castle" anymore... Imo, PCs are just our tools, not our homes.
Have a nice day and Good luck!!!
Last edited by HeM; 05 Nov 2019 at 10:20.
I want to add than hybernation works as it should, only fast startup does not.
Why do you think fast startup is not working?
What exactly is the issue here? I know system restore is not working, what about the bootup though, what is wrong there? Is it taking a very long time to boot?
Keep in mind windows 8.1 support ends on January 10, 2023. Only security updates will be provided till that date. Once that happens, you will need to move to windows 10 on whatever version they are on then.
Quote