New
#340
Hi Kari,
I just wanted to thank you for the effort you've put into finding a solution for build 16215. I'm just going to sit this one out after 4 failed attempts and over 4 wasted hours of my life.
Hi Kari,
I just wanted to thank you for the effort you've put into finding a solution for build 16215. I'm just going to sit this one out after 4 failed attempts and over 4 wasted hours of my life.
@cereberus,
Technically, File History is not an image backup tool either. It was basically just a new version of Windows Backup for Files instead.
System Image is still included in Windows 10 for now though.
Create System Image in Windows 10 Windows 10 Backup Restore Tutorials
Failed to install from 16199 repeatedly but finally installed from 15063 on the first try. Absolutely no idea what the issue is or was.
And...
If you use OneDrive, any files that have been deleted, can be restored if you don't go online, and delete the OneDrives Recycle Bin, and that, without taking up any precious disk space(specially when using SSD's:)) I personally have never used Windows File History, as I have found it a waste of space, and redundant
I have had to go there to get back an older Magician Installer before(and some others as well), even an old Ubuntu ISO I wanted again.
Sure but look at link - it only says restore now. My point is that MS seem to be up to old tricks of trying to quietly drop the image tool again. They were trying to drop it before in W8 but feedback from the old technical programme forced MS to make it more visible.
It just looks stupid and hardly intuitive to click on a link that says restore now to backup when it said backup and restore (windows 7) before (stupid name though).
They have dropped fhb and I think they intend to ultimately drop image creation as well. Of course, the restore option is needed for legacy support.
I believe the only reason they have not dropped imaging yet is because it is being used by people but when timeline is available, they intend to drop it. Why else would the menu have changed to Restore only?
16215 installing on my InsiderPC went painlessly. Before restart I made USB install media and after that I allowed the proces to complete. No problems.
Because my PC had many versions one on the other, I did clean install by the media I made. Now I have clean 16215 on my InsiderPC. There are some little issue eg. Edge Translator does not work but I believe it will be OK.
Details my PC here
MS should do what they did in 1995 with Norton, they just bought it and do same with Macrium and incorporate Reflect into system.
A funny thing I noticed that showed in this build. Cortana keeps pooping up with some suggestions. After I looked at it I found out that it's using my Line-IN instead of microphone that isn't connected. As I have sound from satellite TV going thru it, occasionally it picks up a word from TV and reacts to it.
@cereberus,
File History below is not the same as "Backup and Restore (windows 7)" which is for Windows Backup and Windows System Image.
Backup Files and Folders with File History in Windows 10 Windows 10 Backup Restore Tutorials
We'll just have to wait and see what the new "Timeline" backup feature will be like.
Oh, I hope not. There is a tendency to strip down utilities to basic functionality, then to remove the user interface altogether - defrag was once a hypnotising display of file blocks being shifted around and compacted, changing colour as the process reached completion - now, nothing.
Disk Defragmenter FAQ | Storage at Microsoft[Last updated 4/26/07]*
Why did you simplify the Disk Defragmenter interface?
The Windows Vista Disk Defragmenter was simplified primarily for the purpose of removing it out of the face of the user. It runs periodically and keeps your file system fragmentation at acceptable levels, making it unnecessary for you to launch the tool itself. With the new UI, you can see that we really don’t want defrag to be something that people have to worry about, just like any number of other low-level capabilities in the OS.
The new interface seems “dumbed down.” Why remove all the detail?
Interestingly enough, one of the biggest and consistent complaints we had from users (broad sample here from home users to experienced IT Pros) in the past was that a vast majority of them had no idea what the detailed fragmentation statistics they saw meant. The Windows XP graphical view also had some limitations and inaccuracies that prevented it from being included in Windows Vista. If you really want to keep a close eye on fragmentation, I’d recommend using the command-line tool Defrag.exe.
Why was the defrag progress indicator removed?
Part of the problem with the Windows XP defrag tool was that percent complete was not accurate or meaningful. Depending on the phase of defrag, 1% of progress could take from several seconds to minutes, which made the progress indicator highly unreliable. The difficulty here is that since defrag is a multi-pass process (multiple iterations of file defragmentation and free space consolidation) there is no way to accurately predict when defrag will complete since the number of loop iterations and how long each takes are highly dependent on the layout of the files on the volume, the level of file and free space fragmentation, and the other system activity. While I agree that having no progress is bad, misleading progress I believe is worse. Also, the idea behind the new automated defrag is that users will not have to think about it not worry about the progress it is making. With defrag running regularly, the system will be close to optimal levels of fragmentation, and subsequent defrag runs should not take long.
P.S I miss it too!