cant change time settings (windows 10)

Okay same results ........ got any ideas @MaloK on why access is denied? sfc and dism were good.

steve108 said:

Okay same results ........ got any ideas @MaloK on why access is denied? sfc and dism were good.

third time I see it. It ends with repair install... in place upgrade... I know it's not the dreamed MS Solution but.

Install NetTime 3.14 and forget about it...

I tried to reverse all security on files and registry keys and it did not help... Some have reported the service fixing by itself.!.!.!

If your time gets always messed up you may have a bad CMOS battery or a failing RTC...

But with a good aggressive Time synchronizing sotware like NetTime. It will end your troubles.

Ethan,
Try

Code:

chkdsk c:

first.

If it finds problems, then run

Code:

chkdsk c: /r

to repair the problems. You will have to reboot for that and it may take an hour, hopefully less if you have a SSD boot drive.

Otherwise, I too think that a repair-install should be next if it still doesn't work after chkdsk.

Repair Install Windows 10 with an In-place Upgrade
You should see the option to keep your personal files and apps, so this is not a clean install.

We always recommend to make a full backup first, just in case:
Backup and Restore with Macrium Reflect

Without "/f" nothing will be fixed

MaloK said:

Without "/f" nothing will be fixed

https://docs.microsoft.com/en-us/win...ommands/chkdsk

See what it says about /r
"/r Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors."

Not chkdsk c:

MaloK said:

Not chkdsk c:

If problems found, I said to do "chkdsk c: /r"

Ran the code. Don't think it found any problems.. Where do I type the /f in the script. Becoming a little out of my depth haha

PS C:\WINDOWS\system32> w32tm /resync
The following error occurred: The service has not been started. (0x80070426)
PS C:\WINDOWS\system32> chkdsk c:
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
702976 file records processed.
File verification completed.
Phase duration (File record verification): 14.12 seconds.
22451 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.48 milliseconds.

Stage 2: Examining file name linkage ...
72610 reparse records processed.
996420 index entries processed.
Index verification completed.
Phase duration (Index verification): 28.29 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.29 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.49 milliseconds.
72610 reparse records processed.
Phase duration (Reparse point and Object ID verification): 292.01 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 163.23 milliseconds.
146723 data files processed.
Phase duration (Data attribute verification): 0.66 milliseconds.
CHKDSK is verifying Usn Journal...
41885320 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 371.88 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

116165240 KB total disk space.
96702800 KB in 424817 files.
316548 KB in 146724 indexes.
0 KB in bad sectors.
828204 KB in use by the system.
65536 KB occupied by the log file.
18317688 KB available on disk.

4096 bytes in each allocation unit.
29041310 total allocation units on disk.
4579422 allocation units available on disk.
Total duration: 45.56 seconds (45568 ms).
PS C:\WINDOWS\system32>

Chkdsk found no problems, so next step is repair-install previously linked.

Just downloaded net time and seems to have fixed the issue. Just wanted to thank you guys for all your help over the past few days. Wouldn't have even known where to start