Getting to know the Windows update history pages

Getting to know the Windows update history pages

https://ift.tt/2BOTEx4

At Microsoft, our vision for transparency is what drives us to create extensive documentation for every audience. We believe our documentation should reflect the needs of our customers and range from “get started” guides for our various products and solutions to guidance around specific issues that customers may encounter—for example, when updating Windows devices to solve stability issues and protect against the latest security vulnerabilities. While we’ve talked about the guiding principles for monthly Windows 10 quality updates, it’s important to know that we have specific documentation on what is included in each of those updates and why and how you should install them.

That documentation can be found on the Windows 10 update history page. Despite what the name suggests, the update history page is not a single page, but rather a collection of pages, one for every Windows update we release. Each page offers detailed information about each update, such as the type of update, which operating system versions it affects, improvements and fixes and how to get the update.

Whether you are an IT pro responsible for your organization, or a consumer working with your personal device, we recommend that you bookmark the Windows 10 update history page as there you’ll be able to:

  • Learn about the latest improvements and fixes included in the update.
  • See if an update resolves an issue that may have affected your experience.
  • Understand why your device isn’t receiving the latest and greatest Windows update.
  • Find out proactively if there are known issues associated with an update and see if there is a workaround and timing for resolution.

Using the Windows 10 update history page

Finding the Windows 10 update history page is easy. You can bookmark the direct link to the page, or search for “Windows 10 update history page” on the web.

When you first arrive on the Update History page, you will see a view much like this:

Windows 10 update history page

To find the “home” page for a specific version of Windows (e.g. Windows 10, version 1809 and Windows Server 2019), look at the list located on the top left. If you’re looking for details about that feature update, you can skip the rest of the steps; you’re where you need to be. If you’re looking for information about a specific quality update; however, simply select the desired update from the bottom left.

How to find details on feature and monthly updates

Windows 10 version “home” pages

Beginning with Windows 10, version 1809, we incorporated active tracking of known issues into the Windows 10 update history “home” page for each version. This information includes:

  • Compatibility blocks. Certain hardware configurations may inhibit a successful upgrade due to compatibility issues which must be resolved.
  • Issues under investigation. Whenever open issues change, or new issues are identified, they can be found here along with their current status

These pages also contain notices, pointers to product roadmaps, FAQs, and other relevant information regarding other Microsoft products, such as Surface or Office 365.

Monthly quality update pages (aka “release notes”)

The monthly quality update pages, or “release notes” for short, contain information pertaining to the content of each quality updates, including:

  • Improvements and fixes. While not an exhaustive list (as each update can often include more than 100 fixes), you’ll find information on fixes that solve high impact issues.
  • Known issues. When there is an issue that may impact users should they install an update, we offer details on these issues to help you determine whether it’s in your best interest to install the update or wait for the update containing a fix.
  • How to get the update. We link to the installation packages from the Microsoft Update Catalog and offer relevant information about installation as well as a link to a list of all altered files in that update.

History of the Windows update history page

Prior to our decision to provide Windows as a service, updates came in the form of a single patch solving a single problem. While this model allowed administrators to pick and choose which problems to solve and, therefore, prioritize testing more relevant patches, it resulted in a growing divide between the devices we tested internally (which had all of the latest patches installed) and the device used by our customers (which had a variety of patches installed or not installed). This fragmentation leaked into our documentation. Each individual patch had its own Knowledge Base (KB) article, creating a large quantity of patch-related pages and making it difficult to find the KB article for a specific patch. With the implementation of Windows as a service, we have been able deliver a single article covering all fixes and improvements in a given update, reducing redundancy and making it far easier for you to find and search for the information you need.

After the first few cumulative updates for Windows 10, we received positive feedback on consolidating the information we offer around updates and made the decision to bring our learnings to legacy operating systems. We started by creating Security-only Updates and Previews of Monthly Rollups for Windows 7, utilizing a similar packaging method to that used for Windows 10. This allowed us to, in turn, vastly simplify our documentation and eventually create an update history page for each currently supported version of the Windows operating system:

Little known facts about the Windows update history pages

Now for a few interesting facts:

  • The Windows Update history documentation is localized in 36 languages, and garners extensive use: the Windows 10, version 1809 page alone presently has over 1 million-page views and counting!
  • On average, Microsoft releases 58 new or updated articles a month for the Windows platforms. We coordinate with other Microsoft teams to share best practices that will help ensure that the information we provide is accurate and consistent for our customers.
  • Users can provide feedback on the update history pages and Microsoft will take action on that feedback.

We’re listening. Actively.

We read every comment you leave on our update history pages. Your feedback is critical to helping us build a better product and experience for our customers.

Here are a few of our recent comments:

  • “I’m 85 and I’ve been able to get rid of the blue screen but now my cursor freezes up what do I next?”
  • “Current update is taking over 30 minutes, & computer is still 0% complete”
  • “I have latest iCloud and latest Windows 10. Using Office 365 Outlook, I still cannot sync my calendar and contacts.”
  • “After the last update to windows 10, everything worked great as if it was a completely new install. The next day when I restarted my computer it reverted to the way It was before the update where some programs would not start.”
  • “Nothing to do, everything is perfect”

Examples like these help us identify trends and build better documentation. Further, it allows us to pass along this feedback directly to our engineering and customer support teams such that they can use this information in their planning processes, and to improve your experiences with future updates and versions of Windows.

We appreciate your comments and hope that you will continue to leave us actionable feedback. To leave us comments, simply click the Yes or No button at the bottom up the update history page and you’ll see the following:

how-can-we-improve.PNG

What’s next?

We are always looking to improve our experiences, and our documentation experience is no different. We are currently looking at new ways to present data that’s more relevant to the way that you use Windows. For instance:

  • Adding a section that specifies the value for each monthly update so that you are aware of the benefits in consuming each update.
  • Exploring how to better provide updates on known issues so you can more easily identify when workarounds are available, or when they have been resolved.

More importantly, though, we’d like to hear from you. How can we improve our transparency further? If you currently use the update history pages, how do you use them? If you haven’t used them before, how can we make them a more compelling resource?

If you have the time, please complete the relevant survey below. We look forward to your feedback and are excited for the opportunity to improve your update experience.

take-the-survey.png

Work

via New blog articles in Microsoft Tech Community https://ift.tt/2cKGgvU

February 21, 2019 at 09:40PM

Announcing Windows 10 Insider Preview Build 18841

Announcing Windows 10 Insider Preview Build 18841

https://ift.tt/2U47YsC

Hello Windows Insiders, today we are releasing 20H1 Build 18841 to Windows Insiders who have opted into Skip Ahead. Remember – these builds are from the 20H1 development branch. Some things we are working on in 20H1 require a longer lead time. We will begin releasing 19H2 bits to Insiders later this spring after we get 19H1 nearly finished and ready; once 19H1 is “nearly finished and ready” we’ll also use the Release Preview ring for previews of drivers and quality updates on 19H1.

IMPORTANT: As is normal with builds early in the development cycle, these builds may contain bugs that might be painful for some. If you take this flight, you won’t be able to switch back to the Fast or Slow rings without doing a clean-install on your PC and starting over.

If you are looking for a complete look at what build is in which Insider ring – head on over to Flight Hub. You can also check out the rest of our documentation here including a complete list of new features and updates that have gone out as part of Insider flights for the current development cycle.

General changes, improvements, and fixes for PC

  • Windows Sandbox now supports configuration files! These files allow users to configure some aspects of the sandbox, such as vGPU, networking and shared folders. A blog post to explain this new feature is available here.
  • Windows Sandbox now captures hotkeys in full screen.
  • We fixed an issue where Windows Sandbox would not start on localized builds.
  • We’ve done some work to improve error reporting in Windows Sandbox. Now the error dialog includes the error code and a link to the Feedback Hub.
  • We fixed an issue where Windows Sandbox was unexpectedly throwing an error due to referencing a deleted file under Windows.old.
  • We fixed an issue where if you unpinned groups from Start, apps might end up thinking their tiles were still pinned.
  • We fixed a recent issue where if you hid the search icon in the taskbar, a number of win32 apps would unexpectedly redraw when opening the Start menu.
  • We fixed an issue resulting in the Search pane becoming truncated if launched after rotating the device orientation from horizontal to vertical.
  • We fixed an issue where Settings would sometimes crash when opening “Advanced Display Settings” from Display Settings.
  • We fixed an issue where it wasn’t possible to add a drive to the list of folders to exclude when setting up Enhanced Search in Settings.
  • We fixed an issue where there were unexpected characters in the text under the Storage Sense listing for temporary files.
  • We fixed an issue resulting in certain games no longer rendering UI updates (appearing visually stuck) after using Alt + Tab to quickly switch away and back to the game.
  • We fixed an issue resulting in the taskbar blinking if an AC adapter was attached when the device had less than 20% battery.
  • We fixed an issue resulting in the taskbar disappearing for a second when dismissing Start/Cortana/Search on a secondary monitor.
  • We fixed an issue resulting in File Explorer potentially hanging when trying to rename, delete, or move MKV files in the recent flights.
  • We fixed an issue that could cause Windows logon to forget the last logged on user, and instead would display the sign-in prompt for the default user from the list after dismissing the lock screen.
  • We fixed an issue resulting in CDPUserSVC using an unexpectedly large amount of CPU for prolonged periods of time.
  • We fixed an issue where the newly added popup window shadows might unexpectedly stop appearing after using your PC for some time.
  • We fixed an issue impacting UWP apps resulting in entries under a “…” that launched other apps not working after the first time the secondary app was launched.
  • We fixed an issue resulting in the left and right arrows on the touch keyboard inserting 4 and 6, respectively, in certain languages.
  • We fixed an issue resulting in the game bar record and broadcast options unexpectedly not working in recent builds.
  • We fixed an issue impacting Emoji Panel and Clipboard History reliability.
  • We fixed an issue in Ease of Access’s Cursor and pointer settings, mouse pointer size and color are now retained on upgrade. There is a remaining issue with mouse pointer showing white color instead of the selected color after signing out and signing back in.
  • When using the Magnifier with larger pointers, it pans smoothly as the pointers change shape.
  • We fixed an issue where navigation mode on Orbit braille display could not be changed.
  • We fixed an issue where Narrator paused unexpectedly when reading through a PDF.
  • [ADDED] We fixed the issue that required an additional reboot when performing Reset this PC and selecting Keep my files on a device that has Reserved Storage enabled.

Known issues

  • Launching games that use anti-cheat software may trigger a bugcheck (GSOD).
  • While we’ve done some work to improve night light reliability in this build, we’re continuing to investigate issues in this space.
  • Some Realtek SD card readers are not functioning properly. We are investigating the issue.
  • In Windows Sandbox, if you try to navigate to the Narrator settings, Settings app crashes.
  • Mouse pointer color might be incorrectly switched to white after signing out and signing back in.
  • Creative X-Fi sound cards are not functioning properly. We are partnering with Creative to resolve this issue.
  • You may experience an increase in Start menu reliability issues on this build – a fix will be included in the next flight.

Known issues for Developers

  • If you install any of the recent builds from the Skip Ahead and switch to either the Fast ring or the Slow ring – optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.

No downtime for Hustle-As-A-Service,
Dona <3

The post Announcing Windows 10 Insider Preview Build 18841 appeared first on Windows Blog.

Work

via Windows Blog https://ift.tt/1kprMQR

February 22, 2019 at 01:09PM

WordPress 5.1 “Betty”

WordPress 5.1 “Betty”

https://ift.tt/2E512Vq

A Little Better Every Day

Version 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard.

Following WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.

Site Health

With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.

When you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin.

Editor Performance

Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother.

Expect more performance improvements in the next couple of releases.


Developer Happiness

Multisite Metadata

5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context.

Cron API

The Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.

New JS Build Processes

WordPress 5.1 features a new JavaScript build option, following the large reorganisation of code that started in the 5.0 release.

Other Developer Goodness

Miscellaneous improvements include:

  • Updates to values for the WP_DEBUG_LOG constant
  • New test config file constant in the test suite, new plugin action hooks
  • Short-circuit filters for wp_unique_post_slug(), WP_User_Query, and count_users()
  • A new human_readable_duration function
  • Improved taxonomy metabox sanitization
  • Limited LIKE support for meta keys when using WP_Meta_Query
  • A new “doing it wrong” notice when registering REST API endpoints

…and more!


The Squad

This release was led by Matt Mullenweg, along with Gary Pendergast as Senior Code Reshuffler and Poet. They received wonderful assistance from the following 561 contributors for this release, 231 of whom were making their first ever contribution! Pull up some Betty Carter on your music service of choice, and check out some of their profiles:

0x6f0, 1265578519, 1naveengiri, 360zen, aardrian, Aaron Jorbin, Abdullah Ramzan, Abhay Vishwakarma, Abhijit Rakas, Achal Jain, achbed, Adam Silverstein, Ajit Bohra, Alain Schlesser, aldavigdis, alejandroxlopez, Alex, Alex Shiels, Alexander Botteram, Alexandru Vornicescu, alexgso, All, allancole, Allen Snook, Alvaro Gois dos Santos, Ana Cirujano, Anantajit JG, Andrés, Andrea Fercia, Andrea Gandino, Andrea Middleton, andrei0x309, andreiglingeanu, Andrew Duthie, Andrew Lima, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrey Savchenko, Andy Fragen, Andy Meerwaldt, Angelika Reisiger, Antal Tettinger, antipole, Anton Timmermans, Antonio Villegas, antonioeatgoat, Anwer AR, Arun, Ashar Irfan, ashokrd2013, Ayesh Karunaratne, Ayub Adiputra, Barry Ceelen, Behzod Saidov, benhuberman, Benoit Chantre, benvaassen, Bhargav Mehta, bikecrazyy, Birgir Erlendsson, BjornW, Blair jersyer, blob, Blobfolio, bobbingwide, boblinthorst, Boone Gorges, Boro Sitnikovski, Brad Parbs, Bradley, bramheijmink, Brandon Kraft, Brandon Payton, Brent Swisher, Brian Richards, bridgetwillard, Brooke., bruceallen, Burhan Nasir, Bytes.co, Caleb Burks, Calin Don, campusboy, carolinegeven, ccismaru, chasewg, Chetan Prajapati, Chouby, ChriCo, chriscct7, Christopher Spires, claudiu, Clifford Paulick, Code Clinic, codegrau, coleh, conner_bw, Corey McKrill, croce, Csaba (LittleBigThings), Cyrus Collier, Daniel Bachhuber, Daniel James, Daniel Koskinen, Daniel Richards, Daniele Scasciafratte, danimalbrown, Danny Cooper, Danny de Haan, Darko A7, Darren Ethier (nerrad), Dave Pullig, David A. Kennedy, David Anderson, David Binovec, David Cramer, David Herrera, David Lingren, David Shanske, David Stone, dekervit, Denis Yanchevskiy, Dennis Snell, designsimply, dfangstrom, Dhanendran, Dharmesh Patel, Dhaval kasavala, Dhruvin, DiedeExterkate, Dilip Bheda, dingo_d, Dion Hulse, dipeshkakadiya, Dominik Schilling, Donncha O Caoimh, dontstealmyfish, Drew Jaynes, Drivingralle, drywallbmb, dschalk, dsifford, eamax, eArtboard, edo888, edocev, ElectricFeet, Ella Van Durpe, Eric Andrew Lewis, Eric Daams, Erich Munz, Erick Hitter, ericmeyer, etoledom, Evan Solomon, Evangelos Athanasiadis, ever, everyone, Faisal Alvi, Felipe Elia, Felix Arntz, Fernando Claussen, flipkeijzer, Florian TIAR, folio, FPCSJames, Frank Klein, frOM, fuchsws, fullyint, Gabriel Maldonado, Gareth, Garrett Hyder, Gary Jones, Gennady Kovshenin, Gerhard Potgieter, Girish Panchal, GM_Alex, gnif, graymouser, greg, Grzegorz (Greg) Ziółkowski, Guido, GutenDev, Hafiz Rahman, [email protected], Hans-Christiaan Braun, Hardeep Asrani, Hardik Amipara, Harsh Patel, haruharuharuby, Heather Burns, Helen Hou-Sandi, Henry Wright, Herre Groen, hitendra, Hitendra Chopda, Ian Belanger, Ian Dunn, ibantxillo, Ignacio Cruz Moreno, Igor, Igor Benic, imath, ionvv, Irene Strikkers, isabel104, ishitaka, Ivan Mudrik, J.D. Grimes, Jack Reichert, Jacob Peattie, James Nylen, janak Kaneriya, janalwin, Janki Moradiya, janthiel, Jason Caldwell, javorszky, Jaydip Rami, Jayman Pandya, Jb Audras, Jeff Farthing, Jeffrey de Wit, Jeffrey Paul, Jennifer M. Dodd, Jenny, Jeremey, Jeremy Felt, Jeremy Herve, Jeremy Pry, Jeremy Scott, Jesper V Nielsen, Jesse Friedman, Jimmy Comack, Jip Moors, Jiri Hon, JJJ, joanrho, Job, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, Joel James, Joen Asmussen, John Blackbourn, John Godley, johnalarcon, johnpgreen, johnschulz, Jonathan Champ, Jonathan Desrosiers, joneiseman, Jonny Harris, Joost de Valk, Jorge Costa, Joseph Scott, JoshuaWold, Joy, jpurdy647, jrdelarosa, jryancard, Juhi Patel, Julia Amosova, juliemoynat, Juliette Reinders Folmer, Junaid Ahmed, Justin Sainton, Justin Sternberg, Justin Tadlock, K.Adam White, kapteinbluf, keesiemeijer, Kelly Dwan, kelvink, khaihong, Kiran Potphode, Kite, kjellr, kkarpieszuk, kmeze, Knut Sparhell, konainm, Konstantin Obenland, Konstantinos Xenos, kristastevens, krutidugade, laghee, Laken Hafner, Lance Willett, laurelfulford, lbenicio, Leander Iversen, leemon, lenasterg, lisannekluitmans, lizkarkoski, Luca Grandicelli, LucasRolff, luciano, Luminus, Mário Valney, maartenleenders, macbookandrew, Maja Benke, Mako, mallorydxw-old, Manuel Augustin, manuel_84, Marc Nilius, marcelo2605, Marco Martins, marco.marsala, Marcus Kazmierczak, marcwieland95, Marius L. J., mariusvw, Mariyan Belchev, Mark Jaquith, Mathieu Sarrasin, mathieuhays, Matt Cromwell, Matt Gibbs, Matt Martz, Matthew Boynes, Matthew Riley MacPherson, mattyrob, mcmwebsol, Mel Choyce, mensmaximus, mermel, metalandcoffee, Micah Wood, Michael Nelson, Michiel Heijmans, Migrated to @sebastienserre, Miguel Fonseca, Miguel Torres, mihaiiceyro, mihdan, Mike Gillihan, Mike Jolley, Mike Schroder, Milan Dinić, Milan Ivanovic, Milana Cap, Milind More, mirkoschubert, Monika Rao, Monique Dubbelman, moto hachi ( mt8.biz ), mrmadhat, Muhammad Kashif, Mukesh Panchal, MultiformeIngegno, Muntasir Mahmud, munyagu, MyThemeShop, mzorz, nadim0988, nandorsky, Naoki Ohashi, Naoko Takano, nataliashitova, Nate Allen, Nathan Johnson, ndavison, Ned Zimmerman, Nextendweb, Nick Diego, Nick Halsey, Nick Momrik, Nick the Geek, Nicolas Figueira, Nicolas GUILLAUME, Nicolle Helgers, Nidhi Jain, Niels Lange, Nikhil Chavan, Nilambar Sharma, Noam Eppel, notnownikki, odyssey, Omar Reiss, Omkar Bhagat, on, others, Ov3rfly, Paal Joachim Romdahl, palmiak, panchen, parbaugh, Parham Ghaffarian, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Paradise, Paul Schreiber, Perdaan, Peter Putzer, Peter Wilson, Petter Walbø Johnsgård, Pierre Saïkali, Pieter Daalder, Piyush Patel, poena, Pramod Jodhani, Prashant Baldha, Pratik K. Yadav, Pratik K. Yadav, precies, Presskopp, Presslabs, PressTigers, programmin, Punit Patel, Purnendu Dash, qcmiao, Rachel Baker, Rachel Cherry, Rachel Peter, Rafsun Chowdhury, Rahul Prajapati, Raja Mohammed, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, RavanH, redcastor, remyvv, rensw90, rhetorical, Riad Benguella, Rian Rietveld, Richard Tape, Ricky Lee Whittemore, Rinku Y, Rishi Shah, Robbie, robdxw, Robert Anderson, Robin Cornett, Robin van der Vliet, Ryan McCue, Ryan Paul, Ryan Welcher, ryotsun, Sébastien SERRE, Saša, sagarnasit, Sami Ahmed Siddiqui, Sami Keijonen, Samuel Wood (Otto), sarah semark, Sayed Taqui, Scott Lee, Scott Reilly, Sean Hayes, Sebastian Kurzynoswki, Sebastian Pisula, Sergey Biryukov, Shamim Hasan, Shane Eckert, Sharaz Shahid, Shashwat Mittal, Shawn Hooper, sherwood, Shital Marakana, Shiva Poudel, Simon Prosser, sjardo, skoldin, slilley, slushman, Sonja Leix, sonjanyc, Soren Wrede, spartank, spyderbytes, Stanimir Stoyanov, Stanko Metodiev, stazdotio, Stephen Edgar, Stephen Harris, stevenlinx, Storm Rockwell, Stoyan Kostadinov, strategio, Subrata Sarkar, Sultan Nasir Uddin, swift, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, Taylor Lovett, teddytime, Terri Ann, terwdan, tharsheblows, the, ThemeZee, Thomas Patrick Levy, Thomas Vitale, thomaswm, Thorsten Frommen, Thrijith Thankachan, Tiago Hillebrandt, tigertech, Tim Havinga, Tim Hengeveld, Timmy Crawford, Timothy Jacobs, titodevera, Tkama, to, Tobias Zimpel, Tom J Nowell, TomHarrigan, Tommy, tonybogdanov, Tor-Bjorn Fjellner, TorontoDigits, Toshihiro Kanai, Towhidul Islam, transl8or, Ulrich, upadalavipul, Usman Khalid, Utsav tilava, uttam007, Vaishali Panchal, Valérie Galassi, valchovski, vishaldodiya, vnsavage, voneff, warmlaundry, wbrubaker, Weston Ruter, who, Will Kwon, William Earnhardt, williampatton, wpcs, wpzinc, xhezairi, Yahil Madakiya, Yoav Farhi, Yui, YuriV, Zane Matthew, and zebulan.

Finally, thanks to all the community translators who worked on WordPress 5.1. Their efforts bring WordPress 5.1 fully translated to 34 languages at release time, with more on the way.

If you want to follow along or help out, check out Make WordPress and our core development blog.

Thanks for choosing WordPress!

Drew’s Business

via WordPress News https://ift.tt/KZQObc

February 21, 2019 at 05:57PM

Getting to know the Windows update history pages

Getting to know the Windows update history pages

https://ift.tt/2BOTEx4

At Microsoft, our vision for transparency is what drives us to create extensive documentation for every audience. We believe our documentation should reflect the needs of our customers and range from “get started” guides for our various products and solutions to guidance around specific issues that customers may encounter—for example, when updating Windows devices to solve stability issues and protect against the latest security vulnerabilities. While we’ve talked about the guiding principles for monthly Windows 10 quality updates, it’s important to know that we have specific documentation on what is included in each of those updates and why and how you should install them.

That documentation can be found on the Windows 10 update history page. Despite what the name suggests, the update history page is not a single page, but rather a collection of pages, one for every Windows update we release. Each page offers detailed information about each update, such as the type of update, which operating system versions it affects, improvements and fixes and how to get the update.

Whether you are an IT pro responsible for your organization, or a consumer working with your personal device, we recommend that you bookmark the Windows 10 update history page as there you’ll be able to:

  • Learn about the latest improvements and fixes included in the update.
  • See if an update resolves an issue that may have affected your experience.
  • Understand why your device isn’t receiving the latest and greatest Windows update.
  • Find out proactively if there are known issues associated with an update and see if there is a workaround and timing for resolution.

Using the Windows 10 update history page

Finding the Windows 10 update history page is easy. You can bookmark the direct link to the page, or search for “Windows 10 update history page” on the web.

When you first arrive on the Update History page, you will see a view much like this:

Windows 10 update history page

To find the “home” page for a specific version of Windows (e.g. Windows 10, version 1809 and Windows Server 2019), look at the list located on the top left. If you’re looking for details about that feature update, you can skip the rest of the steps; you’re where you need to be. If you’re looking for information about a specific quality update; however, simply select the desired update from the bottom left.

How to find details on feature and monthly updates

Windows 10 version “home” pages

Beginning with Windows 10, version 1809, we incorporated active tracking of known issues into the Windows 10 update history “home” page for each version. This information includes:

  • Compatibility blocks. Certain hardware configurations may inhibit a successful upgrade due to compatibility issues which must be resolved.
  • Issues under investigation. Whenever open issues change, or new issues are identified, they can be found here along with their current status

These pages also contain notices, pointers to product roadmaps, FAQs, and other relevant information regarding other Microsoft products, such as Surface or Office 365.

Monthly quality update pages (aka “release notes”)

The monthly quality update pages, or “release notes” for short, contain information pertaining to the content of each quality updates, including:

  • Improvements and fixes. While not an exhaustive list (as each update can often include more than 100 fixes), you’ll find information on fixes that solve high impact issues.
  • Known issues. When there is an issue that may impact users should they install an update, we offer details on these issues to help you determine whether it’s in your best interest to install the update or wait for the update containing a fix.
  • How to get the update. We link to the installation packages from the Microsoft Update Catalog and offer relevant information about installation as well as a link to a list of all altered files in that update.

History of the Windows update history page

Prior to our decision to provide Windows as a service, updates came in the form of a single patch solving a single problem. While this model allowed administrators to pick and choose which problems to solve and, therefore, prioritize testing more relevant patches, it resulted in a growing divide between the devices we tested internally (which had all of the latest patches installed) and the device used by our customers (which had a variety of patches installed or not installed). This fragmentation leaked into our documentation. Each individual patch had its own Knowledge Base (KB) article, creating a large quantity of patch-related pages and making it difficult to find the KB article for a specific patch. With the implementation of Windows as a service, we have been able deliver a single article covering all fixes and improvements in a given update, reducing redundancy and making it far easier for you to find and search for the information you need.

After the first few cumulative updates for Windows 10, we received positive feedback on consolidating the information we offer around updates and made the decision to bring our learnings to legacy operating systems. We started by creating Security-only Updates and Previews of Monthly Rollups for Windows 7, utilizing a similar packaging method to that used for Windows 10. This allowed us to, in turn, vastly simplify our documentation and eventually create an update history page for each currently supported version of the Windows operating system:

Little known facts about the Windows update history pages

Now for a few interesting facts:

  • The Windows Update history documentation is localized in 36 languages, and garners extensive use: the Windows 10, version 1809 page alone presently has over 1 million-page views and counting!
  • On average, Microsoft releases 58 new or updated articles a month for the Windows platforms. We coordinate with other Microsoft teams to share best practices that will help ensure that the information we provide is accurate and consistent for our customers.
  • Users can provide feedback on the update history pages and Microsoft will take action on that feedback.

We’re listening. Actively.

We read every comment you leave on our update history pages. Your feedback is critical to helping us build a better product and experience for our customers.

Here are a few of our recent comments:

  • “I’m 85 and I’ve been able to get rid of the blue screen but now my cursor freezes up what do I next?”
  • “Current update is taking over 30 minutes, & computer is still 0% complete”
  • “I have latest iCloud and latest Windows 10. Using Office 365 Outlook, I still cannot sync my calendar and contacts.”
  • “After the last update to windows 10, everything worked great as if it was a completely new install. The next day when I restarted my computer it reverted to the way It was before the update where some programs would not start.”
  • “Nothing to do, everything is perfect”

Examples like these help us identify trends and build better documentation. Further, it allows us to pass along this feedback directly to our engineering and customer support teams such that they can use this information in their planning processes, and to improve your experiences with future updates and versions of Windows.

We appreciate your comments and hope that you will continue to leave us actionable feedback. To leave us comments, simply click the Yes or No button at the bottom up the update history page and you’ll see the following:

how-can-we-improve.PNG

What’s next?

We are always looking to improve our experiences, and our documentation experience is no different. We are currently looking at new ways to present data that’s more relevant to the way that you use Windows. For instance:

  • Adding a section that specifies the value for each monthly update so that you are aware of the benefits in consuming each update.
  • Exploring how to better provide updates on known issues so you can more easily identify when workarounds are available, or when they have been resolved.

More importantly, though, we’d like to hear from you. How can we improve our transparency further? If you currently use the update history pages, how do you use them? If you haven’t used them before, how can we make them a more compelling resource?

If you have the time, please complete the relevant survey below. We look forward to your feedback and are excited for the opportunity to improve your update experience.

take-the-survey.png

Work

via Windows IT Pro Blog articles https://ift.tt/2KronSA

February 21, 2019 at 09:40PM

Resources for Microsoft Live Events in Stream, Teams and Yammer

Resources for Microsoft Live Events in Stream, Teams and Yammer

https://ift.tt/2Sig67p

During a customer onsite today, we discussed some of the different ways to deliver a Microsoft Live Event to increase internal employee engagement. There are three primary ways to engage customers in a Live Event. The first is directly through Microsoft Stream which provides a rich set of options around presentation, encoders, etc.. The second method using Microsoft Teams provides the simplest and quickest path to delivering rich, multi-presenter capable, webcasts. Finally, Live Events can also be instantiated within the context of a Yammer Group for large corporate broadcasts with built in Yammer interactions.

I promised the customer when I left them that I would provide documentation and step by step training around how to deliver using each of these methods. The following is that documentation and I thought I might share here as well.

Happy Webcasting! – Michael Gannotti LinkedIn | Instagram | Facebook | Twitter

Microsoft Live Events Resources:

Work

via New blog articles in Microsoft Tech Community https://ift.tt/2cKGgvU

February 21, 2019 at 01:09PM

Starting a Small Business? This $20 Class Will Teach You How to Help It Thrive.

Starting a Small Business? This $20 Class Will Teach You How to Help It Thrive.

https://ift.tt/2TWMOfX

Barry Moltz shows students how to establish profitable, sustainable ventures across 15 hours of content.

Drew’s Business

via Entrepreneur https://ift.tt/1qEhOCr

February 21, 2019 at 09:39AM

PowerShell Basics: Don’t Fear Hitting Enter with -WhatIf

PowerShell Basics: Don’t Fear Hitting Enter with -WhatIf

https://ift.tt/2IoQ2rv

Chances are you’ve run into this situation. You’ve built a script, or a one-liner, to perform a specific task, but you don’t have a way to thoroughly test it without hitting Enter. That moment before hitting enter can be difficult. Knowing this need, there is a switch available with many PowerShell commands called -WhatIf.

With -WhatIf, PowerShell will run your command in its entirety without executing the actions of the command so no changes occur. It displays a listing of actions to be performed against the affected objects in the console window. This is great for the commands that do not display any output when executed, or if you are unsure of the overall impact of your command.

How do you know if a command supports -WhatIf? That’s pretty simple. Use get-help to view the syntax of the command.


PS> get-help remove-item
NAME
    Remove-Item

SYNOPSIS
    Deletes files and folders.


SYNTAX
    Remove-Item [-Confirm] [-Credential <PSCredential>] [-Exclude <String[]>] [-Filter <String>] [-Force] [-Include
    <String[]>] -LiteralPath <String[]> [-Recurse] [-Stream <String[]>] [-UseTransaction] [-WhatIf]
    [<CommonParameters>]

    Remove-Item [-Path] <String[]> [-Confirm] [-Credential <PSCredential>] [-Exclude <String[]>] [-Filter <String>]
    [-Force] [-Include <String[]>] [-Recurse] [-Stream <String[]>] [-UseTransaction] [-WhatIf] [<CommonParameters>]

    Remove-Item [-Stream <string>] [<CommonParameters>]

As you can see, [-WhatIf] is listed in the syntax for the command. Also it will be available as a tab-complete option when entering the command. If you do happen to enter it with a command that doesn’t support it, you’ll receive the following error:


PS C:\Users\mibender> get-help -Whatif
Get-Help : A parameter cannot be found that matches parameter name 'Whatif'.
At line:1 char:10
+ get-help -Whatif
+          ~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-Help], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetHelpCommand

Now let’s see an example of how this works. A common scenario is needing to clean up a file share by file type. In this case, I want to find all of the video files in an MP4 format and remove them from my c:\recordings directory. Here’s the process you would run through:

First, let’s find all of the MP4 files with Get-ChildItem:


PS> Get-ChildItem -File *.MP4 -Recurse -LiteralPath C:\Recordings\

    Directory: C:\Recordings\car-Talks\Attitude-Control

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 9/7/2018 3:47 PM 58188931 Attitude-Control.mp4
Directory: C:\Recordings\car-Talks\Personal-KanBan
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 10/5/2018 1:56 PM 45875317 Personal-kanBan.mp4
Directory: C:\Recordings\car-Talks\Redmond-Week-1\Redmond-Week-1
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 8/3/2018 9:01 AM 19616170 Redmond-Week-1.mp4

So that shows us all of the MP4 files, but I’d like to see them in a standard tables format with just their name and directory location and not separated by directory. To do that, we use Select-Object:


PS> Get-ChildItem -File *.MP4 -Recurse -LiteralPath C:\Recordings\ | Select-Object Name,Directory

Name                         Directory
----                         ---------
Attitude-Control.mp4         C:\Recordings\car-Talks\Attitude-Control
Personal-kanBan.mp4          C:\Recordings\car-Talks\Personal-KanBan
Redmond-Week-1.mp4           C:\Recordings\car-Talks\Redmond-Week-1\Redmond-Week-1
SoundTest1.mp4               C:\Recordings\car-Talks\Soundtest

That looks better. What I did was use the pipeline and select-object to choose just the properties I wanted from the objects output from the initial command

After I’ve reviewed the list, I think that it includes all the items I want to remove. But being paranoid, I’d really like to know that it is going to remove just those files in a specific directory, and not all the files. That’s where -WhatIf comes in with the remove-item command:


PS> Get-ChildItem -File *.MP4 -Recurse -LiteralPath C:\Recordings\ | Remove-Item -WhatIf

What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Attitude-Control\Attitude-Control.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Personal-KanBan\Personal-kanBan.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Redmond-Week-1\Redmond-Week-1\Redmond-Week-1.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Soundtest\SoundTest1.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\Content-Development-AMA\Content-Development-AMA.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\HYB10-Demos-DryRun1-0.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\HYB10-Demos-DryRun1-1.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\HYB10-Demos-DryRun1-2.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\HYB10-Demos-DryRun1-3.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\DryRuns\HYB10-Dress-Run-GSL-01.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB10\DryRuns\HYB10-DryRun-01.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\MITT\HYB20\HYB20-Demo-SecureScore.mp4".

Based on the output, I’ve verified that on the MP4 files in the c:\recordings directory are being removed. Now I can go back to my command and execute it by removing the -WhatIf switch.

Now, let’s say it’s 2am in your time zone, and you need to perform multiple tasks through the PowerShell Console. If you are like me, 2am is not my ‘peak productivity’ hour so making mistakes, like forgetting the -WhatIf switch, could be dangerous. For those instances, you can modify the $WhatIfPreference variable in your console like this:


PS> $whatifpreference
False
PS> $whatifpreference = 'True'
PS> $whatifpreference
True
PS> Get-ChildItem -File *.MP4 -Recurse -LiteralPath C:\Recordings\ | Remove-Item

What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Attitude-Control\Attitude-Control.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Personal-KanBan\Personal-kanBan.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Redmond-Week-1\Redmond-Week-1\Redmond-Week-1.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\car-Talks\Soundtest\SoundTest1.mp4".
What if: Performing the operation "Remove File" on target "C:\Recordings\Microsoft\Content-Development-AMA\Content-Development-AMA.mp4".

When the command to remove all the files is run and I do not include -whatif since it’s 2am, it defaults to running ALL commands with -WhatIf. Now if you actually want to run the command and remove the files, you add the -WhatIf switch parameter and specify :$false like this:


PS> Get-ChildItem -File *.MP4 -LiteralPath C:\Recordings\Test-Recording\ | Remove-Item -WhatIf:$false -Verbose

VERBOSE: Performing the operation "Remove File" on target "C:\Recordings\Test-Recording\Test-Take-SA.mp4".

```powershell

PS CMD> Get-ChildItem -File *.MP4 -LiteralPath C:\Recordings\Test-Recording\
PS CMD>

One thing to remember with this and other preference variables you define in the console is they only maintain the setting in your current shell. When you close and re-open PowerShell, the preference will reset.

Another thing is a word of caution on using -WhatIf. Because it is functionality that is added into commands, the implementer may not implement it properly. I’ve never run into issues with Microsoft-built commands using -WhatIf like Microsoft Exchange, Active Directory, and many of the built-in commands I use below. However, I cannot speak for code samples you may find in the wild. To be safe, you should test -whatif against a smaller pool of targets vs. trying to modify every Exchange mailbox in your organization.

So the next time you need to perform some PowerShell tasks, add -whatif before you execute, and stop fearing the Enter key.

For more information on the commands used in this post, click on the links below:

For more information on PowerShell, check out the docs here

Work

via New blog articles in Microsoft Tech Community https://ift.tt/2cKGgvU

February 20, 2019 at 10:39PM

Military training helped these veterans launch small businesses

Military training helped these veterans launch small businesses

https://ift.tt/2Eky7hA

Having trouble finding an employer who understands your military skill set?

Why not be your own boss?

That strategy seems to be working for the veterans who showed off their small businesses Tuesday in southeast Washington, D.C., during Bunker Labs’ third-annual Muster Across America Tour.

Rebootcamp Recommendations

The participating veteran-run small businesses included a farm specializing in fresh produce, a subscription murder-mystery service, a home-fitness company, a military-apparel business, a retreat for first responders and a site that matches veterans with employers, among others.

Bunker Labs is a nonprofit dedicated to helping veteran entrepreneurs. It co-sponsored the 2019 Muster tour with JPMorgan Chase, which announced it would be investing $3 million in Bunker Labs to improve and expand its operations.

The event featured a keynote address from Under Secretary of the Army Ryan McCarthy, an ex-Army Ranger with firsthand knowledge of the skills veterans can bring to any job.

Sign up for our Rebootcamp Newsletter
Get all the best info from Rebootcamp in your inbox!

Thanks for signing up!

Fear of missing out?

Fear no longer. Be the first to hear about breaking news, as it happens. You’ll get alerts delivered directly to your inbox each time something noteworthy happens in the Military community.

Thanks for signing up.

By giving us your email, you are opting in to our Newsletter: Sign up for our Rebootcamp Newsletter

“They’re resilient people,” he said. “They can deal with a lot of stress. They know how to organize and plan for a problem.”

McCarthy — who quipped that the smallest business he has ever worked for was the House of Representatives — said he believes supporting small businesses is critical.

“It’s more important than ever,” he said. “When you look at the history of the Department of Defense, we’ve always been at our best when entrepreneurs are working with us. We encourage a lot of folks like you to bring us your ideas and work with us.”

The event included a pitch competition, the winner of which received $5,000. First-place went to Off Duty Blue, an online scheduling portal for police officers. A second-place prize of $2,500 was awarded to Hunt A Killer, a two-year-old business with 60,000 monthly subscribers that delivers murder-mystery boxes to the homes of true-crime lovers.

“We build communities,” said Joshua Holley, a Marine Corps veteran and Hunt A Killer’s executive vice president. “You can get the box and you can play by yourself, but we have a lot of members where this is their weekly date night, their family game night every month, or this is their wine club. So it’s a ton of fun.”

Holley said his military service helped prepare him to launch a business.

“The thing with entrepreneurship is that there’s no normal day,” he said. “The idea of bringing organization to chaos, relying on yourself and your teammates, those are the kind of skills taught in the Marine Corps.”

Joshua Holley, a Marine Corps veteran and executive vice president of Hunt A Killer, shows off his product during the Muster Across America Tour at District Winery in Washington, D.C., on Feb. 19, 2019.
Joshua Holley, a Marine Corps veteran and executive vice president of Hunt A Killer, shows off his product during the Muster Across America Tour at District Winery in Washington, D.C., on Feb. 19, 2019.

Some of the veterans at Muster started their small businesses to solve problems they faced after separating from the military.

Take Juan Biddix Jr., a retired Army master sergeant and the owner of fitness company Sarge FITT. He found that after exiting the military, he wasn’t as motivated to continue his usual workout routine.

“I was used to working out all the time,” he said. “Once I retired, I didn’t feel like going to the gym to work out again. So I had to figure out a way that I could work out at home with something that I like to do. So the FITT Rack allows me to do what I like to do.”

Others, like Army veteran and Beyond Lettuce owner Kelly Smith, discovered their business passions after re-entering civilian life. In Smith’s case, it was providing restaurants and local markets with fresh produce.

“We target the high-end restaurants,” she said. “We do not try to compete with Whole Foods; we’re not really on that sort of scale. We like the original, the unique, the interesting. So the chefs look to us to grow the things they want but can’t find.”

She credited her time in the military for teaching her logistical skills like organization, scheduling and time management.

One of the event’s biggest stars was Thor the service dog, who drew plenty of interest to the Badges United Foundation booth. That small business was founded by Kim DeFiori (Thor’s owner) and Sara Laszaic, two Army veterans who, after being diagnosed with PTSD, created the foundation to provide recreational therapy and lifestyle education to America’s first responders.

Thor the service dog hangs out with his owner Kim DeFiori at the Badges United Foundation booth during the Muster Across America Tour at District Winery in Washington, D.C., on Feb. 19, 2019.
Thor the service dog hangs out with his owner Kim DeFiori at the Badges United Foundation booth during the Muster Across America Tour at District Winery in Washington, D.C., on Feb. 19, 2019.

“There are a lot of nonprofits out there that enhance the wellness of our veterans,” said Laszaic. “But for our first responders, there are hardly any.”

Laszaic also said that the military taught her networking and public-speaking skills that she has found useful in building her foundation from the ground up.

A few of the small businesses were started specifically to assist veterans. Assault Forward, which sells military accessories, was created to let veterans visibly identify as such both to civilians and their fellow vets.

“We hope it starts a conversation with people to give veterans a chance to tell their stories,” said Joe Himpelmann, a former Army field artillery officer and co-founder of Assault Forward. He brought up discipline and accountability as examples of military skills serving him well in the business realm.

Finally, there’s Oplign, founded by ex-Navy Seals Mike Grow and Alex Calfee. The two former defense contractors realized that both veterans and their potential employers were being underserved by current hiring practices, so they developed an online service to potentially streamline that process.

“I worked in a dynamic environment. I have small-team leadership skills. I’ve worked with complex and dangerous equipment. I’m safety-focused,” said Calfee of skills he picked up in the Navy. “So we put all of that information into the jobs that should be seeing them.”

Almost all of these veteran small-business owners advised fellow vets interested in entrepreneurship to just do it.

Or, as Hunt A Killer’s Holley put it: “Don’t tell me what you’re thinking about, tell me what you’re doing.”

Navy Club Ship 35

via Navy Times https://ift.tt/1sC5Wg9

February 20, 2019 at 03:19PM

Announcing Windows 10 Insider Preview Build 18342

Announcing Windows 10 Insider Preview Build 18342

https://ift.tt/2GUMcnJ

Hello Windows Insiders, today we are releasing Windows 10 Insider Preview Build 18342 (19H1) to Windows Insiders in the Fast ring.

[UPDATED] PCs with the following chipsets processor model numbers will not receieve this build due to an issue with Connected Standby: Intel64 Family 6 Model 142 and Intel64 Family 6 Model 158. To check to see if your processor falls into these two buckets:

Step 1: Open Device Manager by right-clicking on the Start button on your taskbar.
Step 2: Open up the Processors group and right-click on one of the processors listed (you will see multiple for each core of the processor in your PC).
Step 3: Click properties and go to the Details tab.
Step 4: Choose “Hardware Ids” in the property dropdown. This will give you the model number of your processor.

If you are looking for a complete look at what build is in which Insider ring – head on over to Flight Hub. You can also check out the rest of our documentation here including a complete list of new features and updates that have gone out as part of Insider flights for the current development cycle (which currently is 19H1).

What’s New in Build 18342

Improving Gaming on Windows 10

Thanks to everyone who signed up to try out our new Windows gaming technology in Build 18334. With today’s new build (Build 18342), we have some fixes that we can’t wait to have folks try out: the game now runs correctly with parental controls enabled, and the install process is more stable (including a fix for the game being stuck in “Pending” instead of downloading).

  • If you have already tried State of Decay and everything worked: we’d appreciate you uninstalling State of Decay and then trying the install again, to make sure everything still works.
  • If you have already tried State of Decay and something didn’t work: please try again and see if your issue has been addressed. If not, it would help us a lot if you let us know using the Feedback Hub in Windows (instructions here in this post). Even if you already sent feedback on the issue before, it’s very helpful to know that it’s still happening on a new version of Windows.
  • If you were not able to get a slot for State of Decay: we’ve opened up more slots now, so just go to the Xbox Insider hub and click Insider content to join. NOTE: we’re still limiting availability as we roll out, so we recommend joining right away. If you miss out this time, don’t worry, we’ll be adding more again soon!
  • If you are trying State of Decay for the first time: just do the following:
    1. Install the Xbox Insider Hub app on the PC you’ll be flighting on.
    2. Sign in to the Xbox Insider Hub with your Gamertag. If you don’t have a Gamertag, see instructions.
    3. Select Insider Content in the upper left.
    4. Scroll to the bottom and select the Windows Gaming program (in the System section).
    5. Join the program.
    6. Follow the instructions in the previous post, skipping any steps you’ve already completed above.

If you see any problems downloading or installing the game, or if important functionality like game saving isn’t working, please be sure to use the Feedback Hub to tell us. And thank you again for helping us find any issues!

Linux Files inside of File Explorer

We added the ability for users to access Linux files in a WSL distro from Windows. These files can be accessed through the command line, and also Windows apps, like File Explorer, VSCode, etc. can interact with these files. Access your files by navigating to \wsl$<distro_name>, or see a list of running distributions by navigating to \wsl$. You can learn more about this here.

Screenshot of File Explorer showing Linux files.

Other Updates for Insiders

New Chrome Extension for Timeline: We’re pleased to announce an extension that collects activities from your Google Chrome browser and adds them to your Timeline in Windows. You can download the new Web Activity extension now from the Chrome Web Store. Just sign-in to the extension on your Chrome browser with your Microsoft account, visit a site in Chrome, then watch it appear on Timeline – and pick up where you left off. Your Chrome activities will also sync with Timeline on Android devices using the Microsoft Launcher app. Give the new extension a try and let us know what you think in the Feedback Hub. This is just one of many updates inspired by Insiders to make Timeline even better!

General changes, improvements, and fixes for PC

  • The new tamper protection setting in the Windows Security app protects your device by helping to prevent bad actors from tampering with the most important security settings. The setting is now on by default for Insider Preview builds.
  • We fixed an issue where Windows Sandbox would not start on localized builds.
  • We’ve done some work to improve error reporting in Windows Sandbox. Now the error dialog includes the error code and a link to the Feedback Hub.
  • We fixed an issue where Windows Sandbox was unexpectedly throwing an error due to referencing a deleted file under Windows.old.
  • Windows Sandbox now captures hotkeys in full screen.
  • Windows Sandbox now supports configuration files! These files allow users to configure some aspects of the sandbox, such as vGPU, networking and shared folders. A blog post to explain this new feature will be available here.
  • We improved the capabilities of the wsl.exe command line interface, by adding new features such as importing and exporting distros and consolidating existing features from wslconfig.exe, such as listing distros and setting defaults.
  • We fixed an issue where if the Magnifier was enabled and set to docked mode, machine would crash and reboot on sign-in creating a boot loop.
  • We fixed an issue resulting in build unable to log into WinRE with an admin account in the last couple of flights.
  • We fixed an issue where if you unpinned groups from Start, apps might end up thinking their tiles were still pinned.
  • We fixed an issue resulting in being unable to re-arrange pinned folders in Start’s tile grid.
  • We fixed an issue where the text explaining the Downloads section of Storage Sense had unexpected characters in it.
  • We fixed an issue where Settings would sometimes crash when opening “Advanced Display Settings” from Display Settings.
  • We fixed an issue where after changing an app’s audio endpoint, it might no longer follow master volume changes.
  • We fixed an issue where it wasn’t possible to add a drive to the list of folders to exclude when setting up Enhanced Search in Settings.
  • We fixed an issue with the Settings header at certain window sizes where long names might be truncated in the middle, rather than wrapping properly.
  • We fixed an issue from the previous flight where right-clicking the desktop would bring up a light colored context menu in dark theme.
  • We fixed an issue impacting Emoji Panel and Clipboard History reliability.
  • We’ve made another fix to address reports of devices getting stuck with “Hibernating…” text on the screen on resume from hibernate.
  • We fixed an issue that could cause Windows logon to forget the last logged on user, and instead would display the sign-in prompt for the default user from the list after dismissing the lock screen.
  • We fixed an issue where an issue where some of the Real-Time Protection options for Malwarebytes Premium are not able to be turned on.
  • We fixed an issue resulting in Internet Explorer’s menu bar not always appearing if enabled.
  • We fixed an issue resulting in CDPUserSVC using an unexpectedly large amount of CPU for prolonged periods of time.
  • We fixed an issue resulting in DWM crashing frequently for some Insiders on the previous flight.
  • We fixed an issue resulting in certain games recently going into a black screen/not responding state if their resolution was lower than 1920*1080 and the game entered fullscreen.
  • We fixed an issue resulting in certain games no longer rendering UI updates (appearing visually stuck) after using Alt + Tab to quickly switch away and back to the game.
  • We fixed an issue resulting in significant video and audio lag when projecting videos from certain devices on recent builds.
  • We fixed an issue where turning off Location from the Action Center might take multiple clicks to react.
  • We fixed an issue resulting in single Unicode character insertion failing for IMEs, the touch keyboard, and the Emoji Panel in certain types of edit controls recently.
  • We fixed an issue resulting in the left and right arrows on the touch keyboard inserting 4 and 6, respectively, in certain languages.
  • We fixed an issue where newly installed apps might not show up in search results.
  • We fixed an issue resulting in the Search pane becoming truncated if launched after rotating the device orientation from horizontal to vertical.
  • We fixed a high impact issue resulting in a decrease in Start reliability in the last couple of flights.
  • We fixed a recent issue where if you hid the search icon in the taskbar, a number of win32 apps would unexpectedly redraw when opening the Start menu.
  • We fixed an issue that could result in unexpected flickering if you used pen or touch in certain win32 apps to launch a second instance of the app when in tablet mode.
  • Have a need to create a file that starts with a dot? File Explorer will now allow you to rename a file to be something like “.gitignore” – previously there would be an error siting that you needed to provide a name.
  • We fixed an issue resulting in File Explorer potentially hanging when trying to rename, delete, or move MKV files in the previous flight.
  • We fixed an issue resulting in some Insiders not being able to open Cortana when in Tablet Mode.
  • We fixed an issue resulting in the taskbar blinking if an AC adapter was attached when the device had less than 20% battery.
  • We fixed an issue resulting in the taskbar disappearing for a second when dismissing Start/Cortana/Search on a secondary monitor.
  • We’re updating the name of the “Windows Light” theme to now be “Windows (light)”.
  • We fixed an issue where Cortana’s icon on secondary monitors wouldn’t update colors after switching between light and dark theme.
  • We fixed an issue where when using light theme + small icons + a vertical taskbar orientation, text written on the taskbar would stay white and thus wouldn’t be readable.
  • We fixed an issue that could result in open apps not being shown on the taskbar (but being visible in Alt + Tab).
  • We fixed an issue resulting in greys having an unexpected slight pinkish/purple-ish tinge on some devices in recent flights.
  • We fixed an issue that could result in DWM crashing after enabling high contrast.
  • We fixed an issue in Ease of Access’s Cursor and pointer settings, mouse pointer size and color are now retained on upgrade. There is a remaining issue with mouse pointer showing white color instead of the selected color after signing out and signing back in.
  • When using the Magnifier with larger pointers, it pans smoothly as the pointers change shape.
  • We fixed an issue where navigation mode on Orbit display could not be changed.
  • We fixed an issue where Narrator paused unexpectedly when reading through a PDF.
  • We fixed an issue where users were unable to join or switch between Windows Insider rings.
  • We fixed an issue where the Windows Security app may show an unknown status for the Virus & threat protection area, or not refresh properly.

Known issues

  • Launching games that use anti-cheat software may trigger a bugcheck (GSOD).
  • Creative X-Fi sound cards are not functioning properly. We are partnering with Creative to resolve this issue.
  • While we’ve done some work to improve night light reliability in this build, we’re continuing to investigate issues in this space.
  • When performing Reset this PC and selecting Keep my files on a device that has Reserved Storage enabled the user will need to initiate an extra reboot to ensure Reserved Storage is working again properly.
  • Some Realtek SD card readers are not functioning properly. We are investigating the issue.
  • In Windows Sandbox, if you try to navigate to the Narrator settings, Settings app crashes.
  • Mouse pointer color might be incorrectly switched to white after signing out and signing back in.
  • We’re investigating reports of the Chinese version of multiple games not working.

Known issues for Developers

  • If you install any of the recent builds from the Fast ring and switch to the Slow ring – optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.

REMINDER: Getting the latest Windows 10 app updates

We have locked down the inbox apps in 19H1. These simplified versions of some of the inbox apps are what will ship with 19H1 when it is released. As a result, Insiders may have noticed that some features have disappeared from these apps. This was probably most noticeable with the Photos app. Insiders can get these features back by going into the settings of an inbox app like Photos and clicking the “Join preview” button.

Join the Bing Insider Program

The 91st Academy Awards will honor the best films of 2018 this Sunday. Find out everything you need to know before the ceremony with Bing. Check out this year’s nominees in each category, explore all nominated films, check out local showtimes, and even see who Bing predicts will go home with an award. Bing also gives you a red carpet rewind to see the best of Oscars fashion. Looking for something more competitive? Test your knowledge with the Bing Oscars quiz or cast your vote with the Oscar’s ballot.

If you want to be among the first to learn about these Bing features, join our Bing Insider Program.

No downtime for Hustle-As-A-Service,
Dona <3

The post Announcing Windows 10 Insider Preview Build 18342 appeared first on Windows Blog.

Work

via Windows Blog https://ift.tt/1kprMQR

February 20, 2019 at 05:06PM

Analyzing a Week of Blocked Attacks

Analyzing a Week of Blocked Attacks

https://ift.tt/2E6lkOD


If you’ve never taken a few minutes to look at the information available in the Wordfence Live Traffic feature, I strongly recommend it. It gives you a detailed look at what attackers are trying to do to break into your site, and how Wordfence is blocking them.

For today’s post we analyzed all of the blocked attacks on Defiant.com for a week. In order to see them in Live Traffic, I simply selected “Blocked by Firewall” from the “filter traffic” drop-down above the data table.

What Attackers Were Up To

For the week there were a total of 223 attacks blocked. I was excited to see that all of them were blocked by the Wordfence real-time IP blacklist. We are used to seeing really high percentages blocked by our blacklist – usually in the high 90s. The real-time IP blacklist is a Premium feature that blocks all requests from IPs that are actively attacking WordPress sites.

Attacks originated from 14 unique IP addresses from around the world. Of the countries represented, Germany was the origin for the most attacks at 85. India was second with 61 and France was third with 45. Other countries represented were Ukraine, South Africa, China, Italy and the United Kingdom.

Next we’ll break down what they were trying to do to break in.

Reconnaissance

Five of the IPs appeared to just be performing reconnaissance, as they were simply requesting our home page or some other page on the site. They were likely just checking to see if the site was up and responding to their requests. Since all of the IPs were on the Wordfence real-time IP blacklist, their requests were blocked and they moved on after a couple of blocked page requests.

Author Enumeration

A Chinese IP attempted to retrieve a list of author usernames for the site. Since the authors of posts are very often also administrators, this information can significantly improve the odds of success for a brute force password guessing attack. The attacks all look like the following:

https://www.defiant.com/?author=1

The attacker worked through fifteen author numbers before giving up and moving on. In the Wordfence “Brute Force Protection” settings, look for the following option to enable this feature:

“Prevent discovery of usernames through ‘/?author=N’ scans, the oEmbed API, and the WordPress REST API”

Once you enable this, Wordfence will block these scans. This option is enabled by default and is available for both free and premium users.

We have blocked 382,131 attacks from that IP in the last 7 days across all of our customers. It seems quite likely that had the attempt to retrieve usernames been successful, attempts to log in using lists of common passwords would have followed.

Login Attempts Via XML-RPC

Sixty Three of the blocked attacks were attempts to log in to the site via the XML-RPC interface, which is an API developers can use to communicate with WordPress sites. We see a high percentage of brute force password guessing attempts hit this interface.

In our case we saw a single IP from Chennai, India attempt 61 login attempts in the period of just over an hour. Two other IPs, one in Hong Kong and another in Italy, made just one attempt each. They most likely moved on because they were blocked.

Login Attempts Via wp-login.php

We had just one IP attempt to login via the interface you use to login your site. The first attempt to login was followed immediately by an attempt to access our home page. The script was most likely checking to see if they were only being blocked from accessing the login page or the entire site. A second attempt following the same pattern occurred just two minutes later. We didn’t see additional attempts from that IP. I assume the attacker’s bot is programmed to move on if it’s blocked twice in a row.

A French IP Probes for Opportunities

A single French IP sent 43 requests in a 33 second burst. The first was a simple home page request, which I assume was an attempt to verify the site was up and accepting requests. Surprisingly the attack continued despite being consistently blocked by the Wordfence firewall. The following are a few examples of what the attacker was up to.

One request was checking for the existence of a known malicious file, commonly used by attackers to upload files to hacked websites. The request looks like this:

https://www.defiant.com/wp-upload-class.php

Another interesting request was looking for opportunities to exploit fresh WordPress installs, which we wrote about in July of 2017. Here’s what the request looks like:

https://www.defiant.com/wp-admin/setup-config.php?step=1

We also saw two attempts to find a copy of searchreplacedb2.php laying around. In July of 2017 we wrote about how hackers use the searchreplacedb2.php script to make malicious database changes. Here’s an example request:

https://www.defiant.com/searchreplacedb2.php

A German IP Probes for Opportunities

A single IP from Hirschfield, Germany attacked our site 85 times in just under two minutes. Most of the attacks were repeats of what we saw from the French IP. So it’s possible that it was a different bot at work for the same attacker. However, this IP also attempted to exploit a number of known theme and plugin vulnerabilities.

All of these attempts to exploit known vulnerabilities were trying to download the wp-config.php file, which is a WordPress file that includes the database credentials for the site. If successful, these attacks would give the attacker an easy route to obtaining administrative control of target website.

In one example, the attacker is attempting to exploit an arbitrary file download vulnerability in the “Epic” theme that was disclosed way back in 2014.

https://www.defiant.com/wp-content/themes/epic/includes/download.php?file=wp-config.php

In another, the attacker is trying to exploit a different arbitrary file download vulnerability – this time in the WP Hide & Security Enhancer plugin. The vulnerability was disclosed less than six months ago.

https://www.defiant.com/wp-content/plugins/wp-hide-security-enhancer/router/file-process.php?action=style-clean&file_path=%2Fwp-config.php

It’s important to note that we are not running any of the themes or plugins this attacker is attempting to exploit on Defiant.com. Many of the attacks on WordPress sites are what we often refer to as “spray and pray” attacks, where the attacker simply tries hundreds or thousands of exploit attempts hoping to get lucky. It’s likely that attack volumes are lower for Defiant.com because it’s protected by the Wordfence real-time IP blacklist. Like you, attackers don’t want to waste resources. If all of their attacks are being blocked they will move on to an easier target.

Conclusion

As you know, WordPress sites are under constant attack. There are many attackers, all of whom deploy different tactics. The free version of Wordfence includes protection for all of the attacks outlined above. For even better peace of mind, and likely lower attack volumes, consider upgrading to Wordfence Premium. For only $8.25 per month (billed annually) you can put the Wordfence real-time IP blacklist to work protecting your site around the clock.

Drew’s Business

via Blog – Wordfence https://ift.tt/1ifmLsK

January 23, 2019 at 11:26AM