Windows 10 October 2018 Update rollout now paused
-
Probably indicating they will recommend something like Recuva to recover deleted files as others have been doing for days now.
means "Don't use computer" ?
-
-
You are making my point hello. Using the computer may damage/affect deleted files. By not using the computer you increase chance of recovering them via tools like Recuva.
Yes, it was my intention.
-
-
![]()
I used to use file history and found it generally OK although it hadn't a clue what happened if you made a disk image and then restored that image with the master index losing all its data for any time period that went missing due to the restore. Browsing the files manually was always an option although a simple copy and paste back to their location throws up problems in file permissions if you subsequently want to alter a restored file. Not a big problem but an annoyance.
My main reason for ditching it was the continuous warnings of it being removed from future W10 builds... so I looked elsewhere and found that AOMEI backup program offers something similar to file history. And the reason I ditched W10 backup and restore... because of similar warnings about it being removed. So AOMEI covered all bases and in practice works better than the Windows versions it replaces.
Not sure if this has been answered later in the thread, but I'm currently 20 or so pages behind after the weekend.
AFAIK File History is not on the W10 deprecation list.
Backup and Restore (Windows 7) is. The bit that does system images and Windows 7 Backup.
Macrium is the alternative.
I still actually don't see BaRW7 disappearing until AFTER W7 refuseniks have upgraded (I use the term upgraded with caveats in the current W10 climate).
Bi-annually is a hectic cycle, hell annually would be just fine IMO. No need to change the lifecycle to less than 2 years but just the one feature update a year is more than sufficient.
I digress. But my first comment still stands.
-
Unfortunately Windows is messing with the overclocking. I was running @ 4600GHz now I'm down to 3700GHz even though the BIOS is set for 4600.
Probably uCode? 17763 contains the 17134 + KB4100347 & KB4346084 patch level
Take ownership of C:\Windows\System32\mcupdate_GenuineIntel.dll and rename to mcupdate_GenuineIntel.dll.disabled and restart. This may revert your uCode to UEFI/BIOS level rather than patched.
-
-
I'm just curious as to how many builds they are actively patching, testing, fixing, etc at any one time? And how they keep it all straight as to which build has which issues?
There's slow ring, fast ring, skip ahead, and likely at least one internal build Insiders don't see, plus the current Consumer build. That all slowly trickle down as near as I can tell. The fast ring build eventually goes to slow ring for example. And they all have "know issues" except "maybe" the current Consumer Build. Microsoft will say it has non but IMHO I don't think thats always true. This thread as an example.
-
I'm just curious as to how many builds they are actively patching, testing, fixing, etc at any one time? And how they keep it all straight as to which build has which issues?
There's slow ring, fast ring, skip ahead, and likely at least one internal build Insiders don't see, plus the current Consumer build. That all slowly trickle down as near as I can tell. The fast ring build eventually goes to slow ring for example. And they all have "know issues" except "maybe" the current Consumer Build. Microsoft will say it has non but IMHO I don't think thats always true. This thread as an example.
Why wouldn't one fix work for all ? Unless of course they shmuck something else up ??
-
![]()
I'm just curious as to how many builds they are actively patching, testing, fixing, etc at any one time? And how they keep it all straight as to which build has which issues?
There's slow ring, fast ring, skip ahead, and likely at least one internal build Insiders don't see, plus the current Consumer build. That all slowly trickle down as near as I can tell. The fast ring build eventually goes to slow ring for example. And they all have "know issues" except "maybe" the current Consumer Build. Microsoft will say it has non but IMHO I don't think thats always true. This thread as an example.
This has been my issue with the whole MS philosophy all along. They claim the released systems are bug free, but they are definitely not. Some bugs can be so severe that they might cause a lot of harm on the system although it might look like they could not affect the system in such way.
MS should really stop adding new features at least 1 month before release date, and focus on patching things up in good time. Even the smallest known bug should be fixed before relase, no matter how tiny it might seem.
-
This has been my issue with the whole MS philosophy all along. They claim the released systems are bug free, but they are definitely not. Some bugs can be so severe that they might cause a lot of harm on the system although it might look like they could not affect the system in such way.
MS should really stop adding new features at least 1 month before release date, and focus on patching things up in good time. Even the smallest known bug should be fixed before relase, no matter how tiny it might seem.
Unfortunately there is no such thing as bug free code. Systems are just too complex for that.
-
Here is a wallpaper I mader for this occasion.
It's called"Windows 10 October 2018 Update Black Screen of Death Metal"(BSODM for short)
Only true metal heads will be able to read it though
