Windows 10: Will windows 10 automatically update "OS Build", system files repair options by build ?

Well, since seems Microsoft is pilling up OS builds, now we have 6 and upcoming 7th OS build would like to understand which OS builds automatically upgrades to next OS build.


So, according to Windows 10 - Release Information


a. Does OS Build 10240 automatically without user actions upgrade to 14393, if not then what OS build (latest?) ?

(and same question to OS builds: 14393, 15063, 16299, 17134, and so forth)

b. Does windows 10 upgrade automatically anything?


(Optionally, if answer is not upgrading automatically)

c. Can OS build 17134 ISO, SFC or dism repair OS builds: 10240, 14393, 15063, 16299 ?


Asking since maintaining the repository of latest and first is usually the case, but after 6 OS builds and upcoming next twice a year is quite amount of images to maintain just for repairing Microsoft systems.

:)

 

Windows OS Builds List

Windows Operating Systems Builds List by Matthew Smith
*Many Builds Are Subject To Change Due To Various Sources
NOTE: the listing titles are in order from the order in the actual list, anything added in v8 will show which beta it was updated in to keep you guys informed on what changes were made where, as of 8.0 BETA 8, 7.1 is obsolete, but will keep it up to show how many changes I've made.


NOTE 2: each new list version doesn't just come up with more builds but might come with renaming/removing/replacing of the builds aswel to show proper release names such as,
Release Candidate, RTM, Pre-Beta, etc.
Enjoy


Windows OS Builds Lists - http://www.T4CFantasy.com/WOS/
Currently 5583 Builds Listed
Microsoft DOS / OS/2 (Currently 118 Builds Listed) 8.4.0 Alpha 1
- Microsoft BASIC (Currently 5 Builds Listed) 8.4.0 Alpha 1
- Microsoft Xenix (Currently 4 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 1.x (Currently 6 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 2.x (Currently 18 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 3.x (Currently 27 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 4.x (Currently 6 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 5.x (Currently 23 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 6.x (Currently 24 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 7.x (Currently 4 Builds Listed) 8.4.0 Alpha 1
- Microsoft DOS 8.x (Currently 1 Build Listed) 8.4.0 Alpha 1

Microsoft Windows Emedded CE (Currently 138 Builds Listed)
- Microsoft Windows Embedded CE 1.x (Currently 4 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded CE 2.x (Currently 9 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded CE 3.x (Currently 6 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded CE 4.x (Currently 9 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded CE 5.x (Currently 45 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded CE 6.x (Currently 3 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded Compact 7 (Currently 32 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Embedded Compact 8 (Currently 30 Builds Listed) 8.4.0 Alpha 1

Microsoft Windows Operating Systems (Currently 5316 Builds Listed)
- Microsoft Windows 1.x (Currently 14 Builds Listed) 8.1.0 BETA
- Microsoft Windows 2.x (Currently 10 Builds Listed) 8.1.0 BETA
- Microsoft Windows 3.x (Currently 59 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows 3.x For Workgroups (Currently 7 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows For Pen Computing 1.0 (Currently 5 Builds Listed) 8.1.0 BETA 4
- Microsoft Windows For Pen Computing 2.0 (Currently 1 Builds Listed) 8.1.0 BETA 3
- Microsoft Windows NT 3.1x (Currently 31Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows NT 3.5x (Currently 78 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows BackOffice Server 1.5 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows NT 4.x (Currently 104 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows BackOffice Server 4.0 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows BackOffice Server 4.5 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows Terminal Server 4.0 (Currently 3 Builds Listed) 8.1.0 BETA
- Microsoft Windows BackOffice Small Business Server 4.0 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows BackOffice Small Business Server 4.5 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows 95 (Currently 224 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows 96 / Nashville (Currently 7 Builds Listed) 8.2.0 Alpha 4a
- Microsoft Windows 97 / Memphis (Currently 12 Builds Listed) 8.2.0 Alpha 4a
- Microsoft Windows 98 (Currently 151 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Me (Currently 58 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows 2000 (Currently 279 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows BackOffice Server 2000 (Currently 2 Build Listed) 8.1.0 BETA 9
- Microsoft Windows Small Business Server 2000 (Currently 2 Builds Listed) 8.1.0 BETA
- Microsoft Windows Neptune (Currently 8 Builds Listed) 8.2.0 Beta 2
- Microsoft Windows XP (Currently 1226 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows XP Embedded (Currently 3 Builds Listed) 8.1.0 BETA 6
- Microsoft Windows Server 2003 (Currently 186 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Small Business Server 2003 (Currently 2 Builds Listed) 8.1.0 BETA
- Microsoft Windows Small Business Server 2003 R2 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows .NET Server 2003 R2 (Currently 5 Builds Listed) 8.0.0 BETA 4
- Microsoft Windows Embedded for Point of Service (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows Embedded Standard 2009 (Currently 2 Builds Listed) 8.1.0 BETA
- Microsoft Windows Embedded POSReady 2009 (Currently 1 Build Listed) 8.1.0 BETA
- Microsoft Windows Vista (Currently 713 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Server 2008 (Currently 483 Builds Listed) 8.1.0 BETA
- Microsoft Windows 7 (Currently 580 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Server 2008 R2 (Currently 364 Builds Listed) 8.1.0 BETA 5
- Microsoft Windows HPC Server 2008 (Currently 8 Builds Listed) 8.0.2 BETA
- Microsoft Windows HPC Server 2008 R2 (Currently 12 Builds Listed) 8.1.0 BETA 5
- Microsoft Windows Hyper-V Server 2008 (Currently 5 Builds Listed) 8.2.0 Beta 1
- Microsoft Windows Storage Server 2008 (Currently 2 Builds Listed) 8.0.2 BETA
- Microsoft Windows Storage Server 2008 R2 (Currently 3 Builds Listed) 8.0.2 BETA
- Microsoft Windows Storage Server 2008 R2 Essentials (Currently 1 Build Listed) 8.0.3 BETA
- Microsoft Windows Small Business Server 2008 (Currently 3 Builds Listed) 8.0.1 BETA 2
- Microsoft Windows Essential Business Server 2008 (Currently 14 Builds Listed) 8.0.2 BETA
- Microsoft Windows Server 2008 Foundation (Currently 1 Build Listed) 8.1.0 BETA 6
- Microsoft Windows Home Server (Currently 20 Builds Listed) 8.0.2 BETA
- Microsoft Windows Home Server 2011 (Currently 10 Builds Listed) 8.1.0 BETA 7
- Microsoft Windows MultiPoint Server 2010 (Currently 2 Builds Listed) 8.0.0 BETA 5
- Microsoft Windows MultiPoint Server 2011 (Currently 6 Builds Listed) 8.1.0 BETA 7
- Microsoft Windows Small Business Server 2011 Essentials (Currently 4 Builds Listed) 8.0.3 BETA
- Microsoft Windows Small Business Server 2011 (Currently 7 Builds Listed) 8.1.0 BETA
- Microsoft Windows Embedded Standard 7 (Currently 6 Builds Listed) 8.0.3 BETA
- Microsoft Windows Embedded POSReady 7 (Currently 3 Builds Listed) 8.1.0 BETA 5
- Microsoft Windows Thin PC (Currently 3 Builds Listed) 8.1.0 BETA 5
- Microsoft Windows 8 (Currently 419 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Server 2012 (Currently 161 Builds Listed) 8.4.0 Alpha 1
- Microsoft Windows Server 2012 Essentials (Currently 2 Builds Listed) 8.4.0 Alpha 1

 

Repair Windows 7/8/10

Repairing Windows 8

Further improving on previously deployed OS repair methods, Windows 8, 8.1, Server 2012 and 2012 R2 further allowed advanced repair where an in-place upgrade or total re-install would be required on previous operating systems. In all honesty, before Windows 10 implementation, this was arguably the easiest OS to repair for a couple of years by running more basic commands.

This has since been advanced to more closely match Windows 10/Server 2016 repairs but with the below information I hope to guide you through performing these advanced tasks more easily!

Spoiler: Windows 8/8.1 Repair DISM

If CHKDSK and SFC fail to repair the issues with the system, then it this is your next option and besides restoring from a previous backup might be the second-to-last option before re-installing the operating system. We will utilize DISMfor this next repair option.

• In some instances, you won't need the OS ISO to perform the DISM image cleanup. You can attempt this on any OS from 8-10 by using the following command in elevated CLI: DISM /Online /Cleanup-Image /RestoreHealth
• In many cases now due to some changes Microsoft made, you'll need to have a copy of the OS ISO available. The ISO will need to be a standard deployment variety that contains Install.WIM in the Sources directory, otherwise the process will fail. Once you have the correct ISO, mount it in Explorer (can do this natively on Microsoft Windows 8.0+), verify the drive letter, verify Image.WIM in the Sources directory.
  • To download a Windows 8.1 ISO from Microsoft, click here.
• Enter the following in elevated CLI: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
  • X = drive letter of mounted ISO. Change to match the appropriate drive letter.
  • Say I had the Install.WIM located in C:\Images, I would type the following command: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:C:\Images\Install.WIM:1 /LimitAccess

The DISM scan can take a while, often times longer than an CHKDSK or SFC scan. To speed up the process, have the Image.WIM on a faster flash media or on local storage rather than disc media. This will help greatly. In many cases one or two runs of this command will repair most issues I've found with Windows 8/8.1.

Once the DISM repair process has been found successful, or not, I will perform a reboot. If the repair was unsuccessful, this will be when I attempt a second pass. If the second pass fails, it is time to move onto the next solution.

However, if the DISM repair passes at any point, reboot the system and then perform an SFC to confirm no further issues are found or need resolved. This step is likely overkill for those not seeking to do optional steps.

Operating System Refresh

It should be noted that in the event DISM fails to repair the system, then an OS refresh would be the next suggestion if the deployed that could save the user's files and OS deployment.

This feature has been an available feature since Windows 8 launched in 2012. The biggest benefit with this option over Windows 7's in-place-upgrade is not necessarily requiring the OS installation media to perform the repair.

If the system is an OEM, an OS refresh from the OEM partition may mean a reinstall of the OS and loss of user data but the restoration of OEM software and bloatware. But you can still choose a manual OS-only refresh without the bloatware if you take the correct steps.

The best choice in my opinion is to run an OS refresh procedure from the advanced boot menu or you can run the installation media while in Windows to perform and Upgrade installation, this will keep your files and settings but replace Windows files and components.

To access the advanced boot menu for Windows 8, there are a several options.

• When choosing restart from the OS GUI, hold down SHIFT and click restart. This method will work even if you cannot log into a profile on the system which makes it very useful in some situations.
• If logged in, access PC Settings, and click Restart Now under Advanced Startup.
• If logged in, open a command prompt window and type shutdown /r /o /t 0 which will initiate a reboot into the advanced menu right with no delay. Without /t 0, there will be a 60-second delay. The number value after the /t is delay seconds.

Once you've reached the advanced boot menu, choose Troubleshoot. From there you can choose to Refresh your PC, Reset your PC and Advanced Options. For this repair, we want to choose Refresh your PC. It's description reads "If your PC isn't running well, you can refresh it without losing our files." That is exactly what we want to accomplish here!

Follow the prompts and processes, and after the refresh installation and rebooting, you should be greeted with a login screen back to your profile in your stable OS environment. At this point you should be able to use the system as intended, if in doubt then re-run the SFC and DISM scans.

In-Place Upgrade

If CHKDSK, SFC and DISM fail to repair the issues with the system, yet you can still boot to the Windows desktop, then the next option is to perform an in-place upgrade. This is more in-depth than an Operating System Refresh. It re-installs most of the operating system's core image and critical files without losing your profiles, data or programs, but do expect to lose some settings. In many cases this process can fix some major issues and refresh an otherwise corrupt and issue-ridden OS installation back to something stable and usable.

Time to close the CLI windows and get back into the GUI, unless you want to deploy Windows through CLI. You'll have to source a different guide for that process!

Requirements to perform an in-place upgrade:

• Must have installation media that matches the installed OS version and type. This applies to both Windows and Windows Server.
• Must be able to get to the desktop on the affected system to correctly initiate this process, booting to the media will not allow an upgrade to be performed.

That last rule is the frustrating part of this repair process if you cannot get that far, backup what you can and do a fresh installation. Otherwise proceed.

• Start the process by using autorun or manually running setup.exe from the installation media.
• Windows 8/Server 2012+ can mount ISO's in Windows Explorer, you can use that instead of physical media options to perform this task.
• You'll come to the installation window, the options will be Upgrade or Custom. Choose Upgrade. This is critical as choosing custom will force you to overwrite, append or wipe out the current install rather than performing any kind of repair.
• Follow the on-screen prompts, which should be very few for you to interact with. The overall process looks and is the Windows install GUI. Once it is completed, the system will automatically reboot (may need to more than once).
• After the reboot(s) after the in-place upgrade you should have a fully functional Windows without issues or corruptions.

Performing an in-place upgrade makes sense, and gives you a stable and clean running operating system when there's an issue or corruption you just can't fix but things aren't broken enough to warrant a fresh installation. The point of this process is to refresh the Windows OS files but retain your data, programs, and settings. That is precisely what the in-place upgrade procedure accomplishes.

I should also add that this process can be accomplished remotely as well, from start to finish. I have done so with persistent LogMeIn, ScreenConnect and Teamviewer installations on various remote systems I have performed this task on, RDP should work as well. Being able to do this level of repair remotely is a huge benefit to any sysadmins out there looking to keep a client happy and perform that "remote magic" IT guys are known for.


**If at this point your issues are not fixed, then there is something else occurring that is causing the issue be it Malware, hardware, drivers, etc. Please refer to the OP in this thread to run through some of those tests and diagnostics, or create a new thread seeking help and stating what you've tried.**

 

Repair Windows 7/8/10

Repairing Windows 7

Methods of advanced CLI repair were introduced with Windows 7 and Server 2008 that can allow sysadmins and end-users to attempt to resolve issues without wiping their hard drive, re-installing and either losing or restoring data.

I will list the important repair processes I use in the field, at my bench, remotely, for family, etc. that have allowed me to keep a current Windows 7 system deployed and running smooth. Keep in mind this is not a cure-all, some issues will require what is called an in-place upgrade. In more severe cases, a system re-install may still be required. For many it is worth the time to try and avoid that process and I am hopeful that some of you will be saved that hassle with this part of the guide!

If you're having issues with Windows 7, hopefully the below repair instructions will help you confirm OS file corruption and help resolve it.

Spoiler: Windows 7 Repair In-Place Upgrade

If CHKDSK and SFC fail to repair the issues with the system, then the next option is to perform an in-place upgrade. This is comparable to an Operating System Refresh in Windows 8/8.1 and 10. In that it re-installs most of the operating system's files without losing your profiles, data or programs. In many cases this process accomplishes just that.

Time to close the CLI windows and get back into the GUI, unless you want to deploy Windows through CLI. You'll have to source a different guide for that process!

Requirements to perform a Windows 7 and Server 2008 in-place upgrade:

• Must have installation media that matches the installed OS version and type. You can download that media click here.
• Must be able to get to the desktop on the affected system to correctly initiate this process, booting to the media will not allow an upgrade to be performed.

That last rule is the frustrating part of this repair process if you cannot get that far, backup what you can and do a fresh installation. Otherwise proceed.

• Start the process by using autorun or manually running setup.exe from the installation media.
• You'll come to the installation window, the options will be Upgrade or Custom. Choose Upgrade. This is critical as choosing custom will force you to overwrite, append or wipe out the current install rather than performing any kind of repair.
• Follow the on-screen prompts, which should be very few for you to interact with. The overall process looks and is the Windows 7 install GUI. Once it is completed, the system will automatically reboot (may need to more than once).
• After the reboot(s) after the in-place upgrade you should have a fully functional Windows 7 without issues or corruptions.

Performing an in-place upgrade makes sense, and gives you a stable and clean running operating system when there's an issue or corruption you just can't fix but things aren't broken enough to warrant a fresh installation. The point of this process is to refresh the Windows 7 OS files but retain your data, programs, and settings. That is precisely what the in-place upgrade procedure accomplishes.

I should also add that this process can be accomplished remotely as well, from start to finish. I have done so with persistent LogMeIn, ScreenConnect and Teamviewer installations on various remote systems I have performed this task on, RDP should work as well. Being able to do this level of repair remotely is a huge benefit to any sysadmins out there looking to keep a client happy and perform that "remote magic" IT guys are known for.

**If at this point your issues are not fixed, then there is something else occurring that is causing the issue be it Malware, hardware, drivers, etc. Please refer to the OP in this thread to run through some of those tests and diagnostics, or create a new thread seeking help and stating what you've tried.**
Spoiler: Update Windows 7 Successfully Update Windows 7 Successfully

Many of us have or will run into it, the endless hours of waiting for the Windows Update process to actually update or fail trying to update a Windows 7 install. Could be a fresh install, or a years-old install. This will eventually happen to you, unless you run a WSUS server, and even then the OS can get held up. Microsoft has been changing how all supported versions of Windows update, trending towards the cumulative monthly releases. This transition seems to be one of the tipping points on the matter.

Regardless, there are some excellent solutions available to help you keep up your Windows 7 installation.

• Solaris17's Windows Update Utility
  • Recommended method for most users that simply want their Windows 7 installation updated. Run as admin, follow directions, be patient.
  • Please comment in that thread if you need assistance or run into issues. Solaris has made many useful changes and revisions due to good feedback.
• Update Windows 7 Manually
  • Manually perform the tasks that Solaris's utility does if you prefer.
• Update Windows 7 Manually
  • Another source.
• Update Windows 7 Manually
  • One last source for good measure!
• Windows 7 Refreshed Media Creation
  • Creating a Windows Image file (WIM) that contains the necessary updates can make future deployments boatloads easier. This is well worth a read for the more technical types and sys admins.

Those links should provide you with some very useful ways to handle updating Windows 7. If you run into any issues updating Windows 7, please start a thread or post in a relevant linked thread if its kept current.