I’ve avoided posting about this for a while mostly because I thought Windows Photo Viewer would get removed. But it’s still there in Windows 10 1909 and it’s still good - even though it doesn’t play animated GIFs and hasn’t been updated since the time of Windows 7. Here’s how to enable it in Windows 10. Enable Windows Photo Viewer To enable Windows Photo Viewer so it shows up as an option to open image file types with, copy and paste the text below as is into a new text file and save it with a .
In a couple of weeks the next update to Windows 10 - Redstone 4, 1803, the Spring Creators Update will be released and later this year Redstone 5, 1809 will be come out, all being well. This continues the pace set last year and the semi-annual release cycle that Microsoft have put into place. For those of you who, like me, might be wondering what would happen to Windows Server’s release cycle.
Microsoft Deployment Toolkit build 8450 is out. You can read more about it here over on the MS Deployment Blog. Installing & Configuring Microsoft Deployment Toolkit and Dependencies. Here are the links the software we’ll be using: Windows 10 1703 Assessment and Deployment Kit (ADK) Microsoft Deployment Toolkit (8450) First we’ll install the Windows 10 1703 ADK which is now fully supported by MDT in build 8450. The setup will need to download additional files so it may take some time depending on your internet connection.
Update 16/01/2018: Updated this post to reflect the release of Microsoft Deployment Toolkit 8450, which fully supports Windows 10 1709. Update 30/10/2017: If SysPrep is consistently failing when building your Windows 10 1709 image, it is most likely due to the Windows Store update process updating the built in UWP apps. This issue is a known issue, but one I’ve managed to dodge when building previous versions of Windows 10. With 1709, I’ve had SysPrep fail every time.
This is a round-up all my previous posts regarding deployment and configuring Windows 10, installing Microsoft Deployment Toolkit and Windows Server Update Services into one post for reference. Installing and Configuring a WSUS Server Installing WSUS from scratch! Resolving WSUS Connection Errors On Windows Server 2012 R2 Installing and Configuring Microsoft Deployment Toolkit Getting Started With Microsoft Deployment Toolkit 8443 and Windows 10 1607/1703 PXE Booting for Microsoft Deployment Toolkit PXE Booting with WDS for UEFI and BIOS Devices Building and Deploying a Windows 10/Windows Server 2016 Reference Image Building a Windows 10 1607 Reference Image with Microsoft Deployment Toolkit 8443 Deploying a Windows 10 1607 Reference Image with Microsoft Deployment Toolkit 8443 Walkthrough: Building a Windows 10 1703 (Creators Update) Reference Image with Microsoft Deployment Toolkit Walkthrough: Building a Windows 10 1709 (Fall Creators Update) Reference Image with Microsoft Deployment Toolkit Walkthrough: Building a Windows Server 2016 Reference Image with Microsoft Deployment Toolkit Customising and Configuring Windows 10 Stuck Windows Updates from WSUS on Windows 10 1607/Windows Server 2016 Windows 10 1607 (Anniversary Update) opens msn.
With Hyper-V it is possible to run VMs inside of VMs without needing to install third-party virtualization software. You might not have the need to run an entire Virtual Machine inside of another, but some upcoming security features of Windows 10 require Hyper-V to be enabled so this could be a way to have those security features on a Windows 10 VM that you otherwise would not be able to take advantage of.
I’ve been testing a preview build of Windows 10 1709 - the Fall Creators Update with Microsoft Deployment Toolkit and putting it through a few task sequences. I’m happy to say that I’ve not encountered any issues, which I did with previous updates. Keep reading for more info on my testing below. The main point of this post is just to say that when the time comes to deploy the Fall Creators Update with MDT, you shouldn’t encounter any issues.
I don’t usually do these news-type posts (plenty of other blogs for that) but here we are… The next major update of Windows 10 version 1709 also known as the Fall Creators Update has been announced for 17th October 2017. As with 1703 (Creators Update), it will roll out over Windows Update in phases and for those of us who’ll be wanting the .iso from the Volume Licensing Service Center, it should be available very close to the main release date.
Page History Update 2020-11-02: Added information relating to Windows 10 20H2 October 2020 Update Update 2020-06-12: Added information relating to Windows 10 2004 May 2020 Update (20H1) Update 2020-01-27: Removed information for old unsupported versions of Win 10 and added a table to show which app maps to the display names in PowerShell. Update 2019-10-06: Updated to include Windows 10 1909 November 2019 Update (19H2) Enterprise edition. Update 2019-05-23: Updated to reflect the apps included in Windows 10 1903, May 2019 Update (19H1) Enterprise edition.
This week I’ve gone pretty deep down the rabbit hole of automating the Start Menu and Taskbar layouts during an MDT Task Sequence. Update 2017-05-02: This also works with Windows 10 1703 (Creators Update) As every device I’m deploying will have the same customisation I wanted to automate it during the build or deploy Task Sequence, rather than applying it via domain Group Policy to reduce limited network bandwidth, keep Group Policy as light as possible and reduce login times as much as possible.
Update 2017-05-02: I’ll attempt to keep this up to date as new versions of Windows come out. This might seem like an odd topic to cover, but I’ve receive quite a few questions about this in recent months. Due to Windows 10 being developed constantly and on a rapid release schedule, it’s important to differentiate between the various major updates. Even though Windows 10 Anniversary Update (1607) seems very similar to what would have been called Windows 10 RTM in the past, there are some big changes, and keeping track of each major update can be tricky when traditionally IT Pro’s are used to a new version of Windows every few years rather than every few months.