Update – Windows ADK For Windows 10 (Version 1511)

windows10_adk

Update / Warning:

Aaron Czechowski, Senior Program Manager, Enterprise Client and Mobility has issued a warning regarding the latest release of Windows ADK for Windows 10, version 1511:

“…….there is a serious issue with it that blocks the following Configuration Manager OS deployment scenarios:

  • From Software Center, launch a task sequence that uses a Windows PE v10.0.10586 boot image. When the computer restarts into Windows PE, it will fail when “Initializing hardware devices” with the error: “Windows PE initialization failed with error code 0x80220014.”

At this time, we do not recommend that Configuration Manager customers use the 1511 version of the Windows 10 ADK.”

Johan Arwidmark, a System Center and OSD expert had also posted a warning on November 15, 2015 on his blog post “Inside Windows 10 ADK Build 10586“.

Warning: Do NOT upgrade your ConfigMgr 2012 R2 SP1 or MDT 2013 Update 1 environments to this build yet. For ConfigMgr, even though it seems to fix the x64 UEFI / PXE and Powershell/.NET issue, which is great, the new ADK does break Computer Refresh scenarios (Bare metal works). The error code is 0x80220014. Research and discussions with the product teams in progress… MDT 2013 Update 1 yet to be validated, but error comments on twitter does not give me a warm and fuzzy feeling.”

——————————————————————————————————————–
Original post: November 20, 2015.

The Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1511 is now available from Microsoft’s “Download Kits and Tools for Windows 10” site.

The Windows ADK now includes:

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

Windows 10 Enterprise Build 1511 ISO Available on VLSC

win10-ent3

Microsoft Volume License customers will now find the Windows 10 Enterprise (build 1511) downloads (ISO files) are now available on the Microsoft Volume Licensing Center (VLSC) portal (as of November 16, 2015).

There are two downloads available for this edition (see image below):

  1. Windows 10 Enterprise (Released Jul ’15)
  2. Windows 10 Enterprise, Version 1511 (Released Nov ’15)

win10-ent2

** Windows 10 Enterprise, Version 1511 is a Current Branch and includes the latest updates and features. For Current Branch for Business, install Windows 10 Enterprise (Released Jul ’15).

  • System Requirements for Windows 10:

    Processor: 1 GHz processor or faster
    Memory: 1 GB ( 32-bit ) and 2 GB (64-bit)
    Drive Space: Up to 20 GB available hard disk space
    Operating System: Windows 10

Please like & share:

Repair Windows Update Agent

Windows-Update

Every now and then, you may discover a computer system that is unable to detect or install available software updates from Microsoft or from your internal Windows Server Update Services (WSUS) repository. You’ll find an error such as 8007000E generated and often times running the Windows Update Troubleshooter FixIt tool is sufficient to fix Windows Update errors, but sometimes a manual approach that requires the deletion of the SoftwareDistribution content and re-registering the Windows Update components is needed, and this can be a tedious task. By using a script, this repair task can be automated.

Here are some batch scripts to help  fix a broken Windows Update Agent on a computer system. The scripts can also be run on a remote system using the ‘psexec‘ tool, which is part of the Sysinternals Suite from Microsoft. Copy and paste the content of your desired batch file below into Notepad and save the file with the “.bat” file extension, for example: repair_wua.bat .

Version 1:

Version 2:

Here’s another Windows Update Agent Reset script available on Technet.
The Windows Update Troubleshooter is available here.

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

How To Fix Network Print Queue Installation Error 0x0000007e on Windows

Problem:

Adding an HP print queue from a Windows Server 2012 R2 print server on a Windows 7 / Windows 8.1 / Windows 10 system fails with the error:

Solution:

Delete the “BIDI” key from:
HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\<QueueName>\CopyFiles

You can essentially delete the “CopyFiles” key as well.
** Please backup the registry before attempting this fix. **

Please like & share:

KB3035131 March 2015 – LogonUI.exe Error

We have discovered an issue with one of the patches from March 2015, KB3035131 against our Windows 8.1 systems in VMware VDI. Upon installation of this patch, Windows 8.1 systems are unusable as they are presented with a LogonUI.exe error on startup as seen below. In order to get the systems in working condition, the only resolution at this point is to revert to a previous snapshot and disable the 3035131 patch from installing on these Windows 8.1 systems.

memory_error_2015-03-13

There’s not much info on the Internet regarding this particular issue, or at least one that I can find, however there are some mentions of the use of StartIsBack or Classic Shell, but we are not using them. It will be interesting to know if others have encountered a similar experience, what are the known causes, and if there’s a fix to rectify this issue.

 

Please like & share:

Unlock God Mode in Windows 8.1

Windows 8 and 8.1 has a hidden God Mode that allows users to access all settings in a single place.  To unlock and access this feature, create a folder on the Desktop and name it as:

God Mode.{ED7BA470-8E54-465E-825C-99712043E01C}

GodMode
Please like & share:

Vista “Bells & Whistles” Workshop

.
This were the participants in my “Windows Vista – Bells & Whistle” workshop at this year’s UVM Mastering The Maze event. I had over 40 participants and my workshop went very well.

Please like & share: