NVIDIA STUDIO and Quadro Graphics Driver 431.86 Is Available – Download Now

NVIDIA has announced the availability of the new STUDIO and Quadro graphics driver, namely version 431.86, which provides an ideal experience for the latest releases of top creative apps, for example Maxon Cinema 4D, Adobe Lightroom, Adobe Substance Designer, DaVinci Resolve Studio 16, and Unreal Engine 4.

In addition to that, the 431.86 build also removes a bug that caused a system crash while installing the drivers on a system with GPUs from mixed architectures (for example Fermi and Pascal).

Regarding compatibility, the STUDIO release is suitable for desktop and notebook configurations, but only the ones running within 64-bit variant of Microsoft’s Windows 10 operating-system. Also, take into account that there are two available packages: one standard and one DCH driver.

As for the Quadro update, the producer has provided several downloadable files targeted at the 64-bit architectures of Windows 7, 8, 8.1, and 10 platforms (both desktop and notebooks), in addition to at Microsoft’s Server 2008 R2, Server 2012, Server 2012 R2, Server 2016, and Server 2019 OSes (just for desktops).

Therefore, save the appropriate executable for the computer’s operating system, run it, watch for all files necessary for the installation to become extracted, and follow all instructions shown on the screen for a complete and successful upgrade.

Once finished, be sure to execute a system reboot to permit all changes to take effect properly. If this task isn’t requested automatically by the wizard, it might be smart to carry on with it manually to ensure that any troubles are avoided.

Having said that, download NVIDIA STUDIO Graphics Driver 431.86 or download NVIDIA Quadro Graphics Driver 431.86, apply it on your device, and try to check our web site to stay “updated one minute ago.”

Massive April 2019 Patch Tuesday Targets 16 Critical Flaws in Microsoft Products

The April 2019 Patch Tuesday rollout includes updates for a total of 74 different vulnerabilities in Microsoft products, including for 2 flaws which are already being exploited in the wild.

Out of the 74 security holes, no less than 16 of them are rated as Critical, with scripting engines and browsers (Ie and Microsoft Edge) accounting for 8 of these.

First and foremost, IT admins should prioritize the deployment of patches for CVE-2019-0803 and CVE-2019-0859, the two Win32k vulnerabilities allowing for privilege escalation. Microsoft says the issues already are being exploited and explains that the successful attack allows a malicious actor to obtain full charge of a compromised host.

However, it’s worthwhile to learn that an attacker would first need to get on the machine before exploiting this flaw.

All Windows versions are impacted, including the Windows 10 October 2018 Update, which is the newest stable release at this time.

Windows 10-specific flaw”

Additionally, Microsoft says there’s additionally a privilege escalation vulnerability in the Windows Appx Deployment Service (AppXSVC) that is getting used for installing Microsoft Store apps. This flaw is detailed in CVE-2019-0841, and Microsoft says Windows 10 version 1703 and newer, in addition to Windows Server 2019 and Windows Server version 1709 and 1803, are impacted.

“An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links. An assailant who successfully exploited this vulnerability could run processes in an elevated context. An attacker could then install programs; view, change or delete data,” the software giant notes.

Microsoft also resolves two different remote code execution (RCE) flaws in GDI+ and IOleCvt, as well as in both cases, an assailant could get full charge of the affected system. All Windows versions are affected as well.

The April 2019 Patch Tuesday updates can be found now from Windows Update, and at the time of penning this article, there are no reports of failed installs or issues experienced after the update.

Microsoft Releases Windows Update KB4471331 to Patch Flash Player Zero-Day

After Adobe resolved a zero-day vulnerability in Flash Player the 2009 week, Microsoft also published an out-of-band patch to deliver the fix to users on Windows systems.

Flash Player has been offered like a built-in component on Windows 8.1 and Windows 10, so Microsoft needs to ship stand-alone patches via Windows Update each time a vulnerability is fixed.

This is what happened this week after Adobe addressed a Flash Player flaw that could have allowed attackers to compromise a Windows host using little else than a malicious Microsoft Office document.

The zero-day code can be baked into Word and Excel documents, but also in other files which are then deployed on vulnerable Windows systems. Adobe warned it’s conscious of several exploits in the wild and urged people to patch their systems as quickly as possible.

Microsoft’s security update is KB4471331 and it is being delivered to all Windows 10 versions available, but also to Windows 8.1, Window RT 8.1, Windows Server 2019, and Windows Server 2016.

“New security updates coming next week”

The organization warns that in the case of Windows 10 version 1607, updates might not be installed automatically, and users are suggested to head to Windows Update to check on for the security patch manually.

Obviously, Windows 10 version 1809 (October 2018 Update) gets the security update as well, and all users are suggested to set up it as soon as you possibly can.

Microsoft will release new cumulative updates containing security fixes next week as part of the monthly Patch Tuesday rollout. However, given that this Flash Player vulnerability has already been being exploited, customers aren’t recommended to obstruct the patching.

However, if system admins can’t install the brand new security patch, they are recommended to bar the opening of documents originating from untrusted sources, but additionally to restrict access to websites that could attempt to deploy malicious payloads in an attempt to exploit the vulnerability.

Microsoft releases Windows Server Insider Preview build 18317

Microsoft released Windows Server Insider Preview build 18317 today, and also the build number corresponds to last week’s client build in the Fast ring. It is the first new build in over a month, as build 18298 was launched on December 18.

There are a few new features to notice in the new build. To begin with, there’s now a dark theme preview. Users can activate it by entering the experiment key msft.sme.shell.personalization in global settings under the advanced tab. Microsoft can also be requesting that users don’t report bugs on it, becasue it is a “work in progress”.

There’s two new PowerShell modules for automating Windows Admin Center, not to mention, there are new Windows Admin Center features. The preview released today is version 1812, and it offers the following features:

Power configuration tab around the server settings page, where you can change the configured power profile.

If the server has an IPMI-compatible BMC, you’ll find the BMC serial number along with a hyperlink to the IP address around the Server Overview page.

If Windows Admin Center is installed in service mode, you can now use PowerShell to automate the next (examples included below):

Import/export of connections (with tags)

Extension management

Finally, Windows Server includes a new feature called WDAC, “composable (stacked) code integrity policies for supporting multiple code integrity policies”. Here’s the changelog:

WDAC brings the capability to support multiple CI policies. Three scenarios are actually supported:

Scenario 1 – Deploy a “base” policy in enforcement mode and deploy another “audit” policy side-by-side to aid validation of changes to our policy before deploying in enforcement mode. (Intersection)
Scenario 2 – Enforce 2 or more “base” policies simultaneously to allow simpler policy targeting for policies with different scope/intent, e.g., Base1 corporate standard policy that is relatively loose to accommodate all organizations while forcing minimum corp standards (e.g. Windows works + Managed Installer + path rules). Base2 team specific policy that further restricts what’s permitted to run (e.g. Windows works + Managed Installer + corporate signed apps only) (Intersection)
Scenario 3 – Supplemental policies deployed to grow Base policy, e.g., Azure host baseline policy restricts tightly to just allow Windows and hardware drivers allows supplemental policies. Exchange Azure team supplemental policy adds only the additional signer rules required to support Exchange team signed code. (Union)

You are able to download Windows Server Insider Preview build 18317 and Windows Admin Center version 1812 here. Also available are downloads for Server Core App Compatibility FoD Preview Build 18317 and Server Language Packs Build 18317.

Manage Azure Virtual Machines Using Windows Admin Center

Since Windows Server 2019 is usually available, it seems like a good time to begin using Windows Admin Center (WAC) because the default management tool. WAC is really a web-based tool for managing local or remote servers using a gateway that utilizes PowerShell Remoting and Windows Management Instrumentation (WMI) over WinRM. And while Windows Server 2019 still includes Server Manager, Windows Admin Center is where Microsoft is now investing its efforts.

In this article, I’m going to demonstrate how to manage Windows Server 2019 running in an Azure VM. I’ll make use of a WAC gateway installed on my Windows 10 PC. This requires the VM you want to have the ability to possess a public Ip and you need to make the necessary management ports available over the Internet. Naturally, this isn’t the most secure option, but it is a quick way to start managing Windows Server. In case your VM doesn’t have a public Ip or you desire a safer method to manage your cloud servers, you’ll have to install a WAC gateway on an Azure VM and/or connect the local network towards the Azure VNet using ExpressRoute, Site-to-Site VPN, or Point-to-Site. But that’s past the scope of this article.

Configure Windows Firewall for Inbound WinRM

Let’s begin by configuring Windows Firewall to permit an inbound connection for WinRM.

Start the Windows Server 2019 Azure VM that you would like to handle while using Azure management portal.
Log in to the Windows Server 2019 virtual machine that you want to manage using Remote Desktop by clicking Connect on the Overview screen for the VM in the management portal.
In Windows Server, open a Windows PowerShell window with admin privileges.

Note that the Windows Server 2019 Azure marketplace image has WinRM enabled automatically. If you wish to manage another supported version of Windows Server, you may want to manually run winrm quickconfig within an elevated command prompt to allow WinRM.

Run the Set-NetFirewallRule cmdlet as shown below to allow inbound WinRM access with the Windows Firewall.

PowerShell
1 Set-NetFirewallRule -Name WINRM-HTTP-In-TCP-PUBLIC -RemoteAddress Any

Configure Azure Networking to Allow Inbound WinRM

Before we are able to connect WAC to Windows Server, we also have to configure Azure networking to permit inbound WinRM connections.

Select your VM in the Virtual Machines portion of the Azure management portal.
On the VM’s page within the portal, click Networking under Settings.
Make sure that Inbound port rules is chosen and then click Add inbound port rule.
On the Add inbound security rule pane, type 5985 in the Destination port ranges
In the Name field, type Port_5985.
Click Add.

The brand new rule will now come in their email list of inbound rules.
Connect to Windows Server using WAC

Now all that’s left to complete is test whether I can connect to the server using WAC. I’ve already installed a WAC gateway on my Windows 10 PC. For additional info on installing a WAC gateway, check out Getting Started with the Windows Admin Center on Petri.

Connect for your WAC gateway from the supported browser.
On the All Connections screen, click + Add. Should you don’t see the All Connections screen, click Windows Admin Center within the top left corner.
In the Add Connections pane, click Add Server Connection.
In the Server name box, type the public Ip or DNS name of the server you want to manage.
If you use an IP address, select Don’t attempt to resolve the server name. You will get the Ip or DNS name from the VM around the Overview pane in the Azure management portal. If you haven’t assigned the VM a static Ip, don’t forget that the Ip will probably change every time the VM begins.

You may get an error message stating that the bond cannot be verified. This really is normal if you’re connecting to the VM the very first time and you can safely neglected.

Click Submit.
The server will now come in their email list of connections. Click the box to the left of the listing to pick it after which click Manage As.
On the Specify your credentials pane, click Use another account for this connection, enter webmaster user name and password for the Windows Server VM, and click Continue.
Select the server again within the list of connections after which click Connect.
You’ll be taken to the Server Manager screen for the remote server.

Microsoft is updating WAC on a regular basis, so it’s worth coming back to it often to check out what is new.

Microsoft Resumes Rerelease of Windows 10 Version 1809

Microsoft on Wednesday once more resumed its general rollout of the Windows 10 version 1809 upgrade, also referred to as the “October 2018 Update.”

In addition to this Windows 10 rerelease, upgrades to Windows Server 2019 and Windows Server version 1809 (the “semiannual channel” form of the merchandise) were resumed on Wednesday, too, based on information added to the “Windows 10 and Windows Server 2019 Update History” page. This history page now includes more descriptive details about Microsoft’s OS releases, including when Microsoft may be blocking a release due to software flaws, bad drivers or application incompatibility issues.

Wednesday’s rollout constitutes the 2nd rerelease of Windows 10 version 1809. Microsoft first released it on Oct. 2. Later, Microsoft pulled that release due to loss of data issues, after which rereleased it on Nov. 13.

Microsoft is now resuming Windows 10 version 1809 releases in “phased rollouts,” and the new OS also will arrive to “seekers.” A so-called seeker is somebody that simply uses the “Check for Updates” capability that’s included in Windows interface, that will trigger a computerized download of the new OS, even if it’s unwanted.

Even though Jan. 16 is easily the most current release date of Windows 10 version 1809, organizations utilizing it will still have their update cycle clocks tuned by Microsoft towards the previous Nov. 13 release date, Microsoft previously explained. It’s an important planning detail for organizations, since Windows 10 must be upgraded after either 18 months or 30 months, with respect to the Windows edition used and if the release was a fall channel release or otherwise.

Based on the history page, there are still blocks in place for Windows 10 version 1809 for some systems, namely systems that have the next dependencies:

Intel display drivers versions 24.20.100.6344 and 24.20.100.6345.
F5 VPN clients which use a split-tunnel configuration.
Trend Micro’s OfficeScan and Worry-Free Business Security software.
AMD Radeon HD2000 and HD4000 series graphics processing units.

Those blocks remained as in effect from in December. Microsoft uses its “telemetry” data gathered from systems to evaluate whether or not they will be ready to get a new Windows OS upgrade or otherwise. Blocks get set when potential upgrade troubles are detected.

Woody Leonhard, a longtime Windows patch observer and Computerworld writer, advised caution in a article about permitting Windows 10 version 1809 upgrades to happen, even though Microsoft has spent about three months addressing its problems. Consumer users of the Home edition, though, do not possess easy options to block its arrival.

After problems with the discharge of Windows 10 version 1809 became apparent in November, Microsoft had announced intends to be more transparent about Windows 10 servicing and quality issues. A brief history page now seems to serve that function.

Microsoft has added a hyperlink within the history page to obtain feeds, which may be utilized in RSS readers to determine when this page gets updated. Clicking that link leads to this page, which provides the user an option to obtain the feed in either Atom or RSS formats. At press time, though, the Feed option for Windows 10 didn’t have any effect, so it’s apparently a piece happening.

US-CERT Alerts of Protection Defects within Windows

The United States Computer Crisis Readiness Group (US-CERT) offers released a good advisory on weaknesses impacting Microsoft Windows and Windows Server.

The organization states “a remote assailant might take advantage of these weaknesses to consider control of an impacted system.”

The said vulnerabilities happen to be fixed through Microsoft as part of the Dec 2018 Area Tuesday cycle, and the organization provides more details within CVE-2018-8611 as well as CVE-2018-8626 advisories.

First and foremost, CVE-2018-8611 is a Windows kernel height associated with opportunity which impacts just about all supported Windows customer as well as server variations, such as Windows 10 as well as Windows Server 2019.

“An height of opportunity weakness exists when the Windows kernel does not properly manage objects within storage. An attacker who successfully used this particular weakness might run arbitrary signal within kernel setting. An attacker could then set up applications; view, change, or remove data; or produce new company accounts along with full user rights,” Microsoft explains.

A successful attack requires a malicious acting professional to log on somewhere and then run a crafted software that would supply complete control over the affected machine. Microsoft states the actual flaw was already exploited, but given it wasn‘t openly revealed, the outcome has been significantly reduced.
“Patches accessible now”

In the case of CVE-2018-8626, Microsoft is actually resolving a Windows DNS server pile flood vulnerability that only exists in Windows 10, Windows Server Next year R2, Windows Server 2016, as well as Windows Server 2019.

“A distant code delivery weakness exists in Windows Domain Name Program (DNS) servers once they fail to correctly manage demands. An assailant who successfully used the weakness might run arbitrary signal in the context of the Local Program Account. Windows servers that are set up because DNS machines are in risk from this vulnerability,” Microsoft states.

The actual attack relies on malicious demands that are delivered to a Windows DNS server actually without authentication.

Patches for the two weaknesses can be downloaded at this time through Windows Revise on just about all backed Windows versions.

Windows Server 2019 to guide OpenSSH natively

In a short article today Microsoft announced that Windows Server 2019 will officially offer OpenSSH as a general supported feature.

OpenSSH can be described as powerful tool that originated as part of the OpenBSD project and has been meant for many years all through the BSD, Linux, macOS, and Unix ecosystems. Adding OpenSSH to Windows Server 2019 allows organizations that work across a range of computer operating systems to use a consistent tools for remote server administration.

The Win32 port of OpenSSH was initially included in the Windows 10 Fall Creators Update and Windows Server 1709 just like a pre-release feature. In your Windows 10 1803 release, OpenSSH was released as a supported feature on-demand component, but there are not a supported release on Windows Server so far. Now the OpenSSH client and server turn out to be available currently being a supported Feature-on-Demand in Windows Server 2019 and Windows 10 1809.

To help get the latest information about OpenSSH in Windows, drive to the Win32-OpenSSH wiki or Microsoft docs. There is undoubtedly a most current documentation or perhaps information about our broader efforts for bringing OpenSSH to Windows.

Microsoft launches Visual Studio 2019 Preview 1 for Windows and Mac

At its Microsoft Connect(); 2018 virtual event today, Microsoft announced the very first public preview of Visual Studio 2019 – it is easy to download it now for Windows and Mac. Separately, .NET Core 2.2 has hit general availability, and .NET Core 3.0 Preview 1 is actually available today.

Microsoft launched Visual Studio 2017 in March 2017 and Visual Studio 2017 for Mac in May 2017 and thereafter released seven subsequent updates for boosting their performance. That has the “most popular Visual Studio release ever,” but in June the firm announced Visual Studio 2019 for Windows and Mac.

As before, Visual Studio 2019 previews will install as well with Visual Studio 2017, which is certainly great for trying out new functionality without messing together with production workflow. Visual Studio 2019 also won’t require a major operating-system upgrade, Microsoft promised. Visual Studio 2017 labored on Windows Server 2012 R2 (and then), Windows 7 (and then), and Mac OS X El Capitan 10.11 (and later).

New features

Visual Studio 2019 brings numerous productivity improvements, enhanced collaboration, and faster tooling, Microsoft promised today. The public preview comprises of a new start window experience to acquire developers in their code faster, increased coding space, completely new search experience, more refactoring capabilities, smarter debugging, AI-powered guidance on IntelliCode, and built-in access to Visual Studio Live Share.

New start window on launch was created to work better with today’s Git repositories, including local repos, Git repos on GitHub, and Azure Repos. Git aside, you may still open a project possibly a solution or launch a new one of either.

Visual Studio’s UI and UX have also received subtle changes, just like a new product icon, a cleaner blue theme, coupled with a more compact title and menu bar. There’s plus a new search experience that replaces the fast Launch box. It means that you can find settings and commands and install options, that’s why even supports fuzzy string searching.

Visual Studio 2019 enhances the code maintainability and consistency experiences with new refactoring capabilities – for example , changing for-loops to LINQ queries and converting tuples to named-structs. There’s one more new document health indicator and code clean-up functionality.

As to debugging, stepping performance is enhanced and search capabilities have been completely added to the Autos, Locals, and Watch windows. You too can expect improvements for your Snapshot Debugger to concentrate on Azure Kubernetes Service (AKS) and Virtual Machine Scale Sets (VMSS), and better performance when debugging large C++ projects, mainly because of an out-of-process 64-bit debugger.

IntelliCode and Live Share

At its Build 2018 developers conference in May, Microsoft previewed IntelliCode and Live Share. Ad units uses AI to provide intelligent suggestions that improve code quality and productivity, and therefore the latter lets developers collaborate right away with other people who can edit and debug totally Visual Studio and Visual Studio Code.

Visual Studio IntelliCode becomes custom models and expanded language support. Custom models further enhance the AI-enhanced IntelliSense, giving developers personalized recommendations in accordance with the patterns and libraries applied to their code, on top of the analysis made on numerous open source repos. Visual Studio developers now get IntelliCode for XAML and C++ code, and even C#. Visual Studio Code developers can utilize IntelliCode when developing JavaScript, TypeScript, Python, and Java.

Potential fans and patrons preview of Visual Studio Live Share, and that is essentially available like an extension for Visual Studio Code, has become new features which might help developers collaborate immediately, including sharing desktop apps, source control diffs, and code commenting. It’s also wise to start a session and think about who you’re employing in a dedicated space near the top right of your respective user interface. Since Live Share is installed alongside the IDE by default, the features can be found in Visual Studio 2019.

Also, Microsoft did not give you a timeframe for Visual Studio 2019’s release. Since its name implies, we can expect it to arrive next year, possibly at Build 2019.
.NET Core 2.2 and .NET Core 3.0 Preview 1

Microsoft today released .NET Core 2.2 with diagnostic improvements on the runtime, support for ARM32 for Windows, and Azure Active Directory for SQL Client. Other improvements include enabling tiered compilation by default, as well as the latest features in the ASP.NET Core web stack, most notably hosting model improvements for IIS; Web API improvements, including API security; template updates for Bootstrap 4 and Angular 6; and HealthCheck upgrades. .NET Core 2.2 has also data stack enhancements, Entity Framework Core, and support for spatial extensions in SQL Server and SQLite. For additional information, check out the release notes.

Announced at Microsoft’s Build 2018 developer conference in May, .NET Core 3.0 could possibly be the next generation about the .NET Core platform. It promises significant updates to web, cloud, IoT, AI/ML, and Windows desktop workloads.

Microsoft today launched .NET Core 3 Preview 1 for Windows, Mac, and Linux. You’ll be able to develop .NET Core 3 applications with Visual Studio 2017 15.9, Visual Studio for Mac, and Visual Studio Code.

.NET Core 3.0 adds support for Windows Presentation Foundation (WPF) and Windows Forms (which today were open-sourced), bringing Windows desktop development to .NET Core. It enables more flexible deployment with side-by-side and self-contained EXE and much better performance. For more information, check out the release notes.

Amazon’s cloud unit launches Arm-based server chips

Amazon’s cloud business will be coming out with cheaper computing options, as a result of server chips that employ the energy-efficient Arm processing architecture.

Amazon Web Services, the clear market leader for public cloud infrastructure, can be the first of the key cloud providers to produce Arm-based computing resources. Microsoft, Google, IBM along with companies compete with Amazon that provides public cloud infrastructure, which companies depend on to store their data and run their applications.

Across these clouds – in addition to corporate on-premises data centers – customers’ computing workloads often operated with Intel-based chips. But SoftBank-owned Arm, whose technology is widely used for chips in smartphones and tablets, is certainly thought of as a prospective alternative designed to run when you use less energy, which can lead to lower costs.

AWS’ EC2 A1 computing instances be determined by the Arm-based Graviton processor from Annapurna, AWS’ chip-development group, Peter DeSantis, the group’s vp of global infrastructure and client service, said in any keynote presentation in the AWS Reinvent user conference in Las Vegas on Monday. For certain workloads, like web servers, costs might be as much as 45 percent lower, DeSantis said.

Amazon bought Annapurna in 2015. Earlier, Amazon hired multiple people from Calxeda, a start-up this led to working on Arm-based server systems.

While commerce still generates all of Amazon’s revenue, AWS happens to be critical to send out financial health. During the third quarter sudden expenses of Amazon’s operating profit came from AWS. While revenue from Amazon’s web shops increased Ten % year over year with the quarter, AWS had revenue regarding 46 percent. AWS presenting more than 125 services obtainable by customers, as an example core EC2 computing service. The A1 instances can be obtained now from four of AWS’ data center regions worldwide.

Earlier this year AWS announced the roll-out of computing instances who make use of servers containing AMD chips.

In 2010 Microsoft demonstrated its Windows Server operating-system running on Arm servers, but Arm-based computing is simply not currently possible from Microsoft’s Azure public cloud.