Créer mon blog M'identifier

register at the Windows Insiders for Business program

Le 14 août 2017, 06:03 dans Humeurs 0

Software Defined Data Center (SDDC) host Security Shielded Linux VM SDN: Encrypted virtual networks Secure clusters SMB 1 disabled by default Resiliency and Availability SDN: Reduced downtime for tenant connections through gateways Spaces Direct: Scoped Spaces to mitigate impact of multi-node loss Spaces Direct: Marginal drive handling for predictive detection of drive failures Efficiency Data Deduplication available for ReFS New Data Deduplication DataPort API for optimized ingress/egress Space efficiency with ReFS Compaction Performant Spaces Direct Multi Resilient Volumes (MRV) Hyper-converged Scale Cluster Sets: Significantly increases hyper-converged SDDC cloud scale by grouping multiple clusters into a larger fabric Hardware support Support for Storage Class Memory (SCM) in Spaces Direct What's New in Build 16257 for Windows Server

Windows Subsystem for Linux (WSL) is available on Windows Server

Windows Subsystem for Linux (WSL) is now available on Windows Server along with a compliment of Linux distributions. Test WSL on Windows Server. WSL runs unmodified Linux (ELF64) binaries natively. With the additions of WSL you can run node.js, Ruby, Python, Perl, Bash scripts or other tools that expect Linux behaviors, environment, or filesystem-layout, the ability to install and run Linux with WSL expands the tools at your disposal on Windows Server. At this time, WSL does not support persistent Linux services (such as daemons and jobs) as background tasks. To enable WSL and install a Linux distribution, see Enable the Windows Subsystem for Linux and Install a Linux distribution in the Windows Server 2016 Installation Guide on GitHub. Read more in this blog or follow the installation guide to try it out.

How to Download

The latest Windows Server build and matching symbols are available for download here. Matching Windows Server container images will be available via the Docker Hub. For more information about Windows Server containers and Insider builds, please visit http://aka.ms/containers/insiders.

The following keys are available for unlimited activations of Windows Server. These keys may be used throughout the pre-release cycle.

Server Datacenter Core: B69WH-PRNHK-BXVK3-P9XF7-XD84W Server Standard Core: V6N4W-86M3X-J77X3-JF6XW-D9PRV NOTE: If you signed up for Windows Insiders for Business using an AAD account, there is a temporary issue with access to the Windows Server Download page using AAD accounts. If you registered using an MSA account at the Windows Insider program, your MSA account may be used to access the page and to download builds until this is resolved.

It's all about your feedback!

Use the Feedback Hub app to provide feedback on Windows Server builds. Feedback Hub comes pre-installed on Windows 10. Register a Windows 10 device with the Windows Insider or Windows Insider for Business programs. Open the Feedback Hub application. Choose the Server category and then the appropriate subcategory for your feedback. Please indicate what edition and build number you are providing feedback on. The Feedback Hub app cannot scan a server for diagnostic information, however you may manually attach screenshots or other files to your feedback entry.

We encourage you to visit the Windows Server Insiders space on the Microsoft Tech Communities forum to collaborate, share and learn from experts.

The expiration date for this server preview build is 12/4/2017.

Known issues

The background tasks infrastructure service (Bisrv.dll) may cause a system crash because of a null class pointer read error (0xC0000005) or a failfast corrupt list entry (0xC0000409) during a Distributed Component Object Model (DCOM) launch, or because of a critical process bug check (error code 0xC0000409, bug check 0xEF) in the host process for Windows services (Svchost.exe). Calling into the firewall service may hang: Apps that call into the firewall, such apps that use networking, may become unresponsive until the user reboots because of an application hang end-task error (0xCFFFFFFF) in the Windows firewall API library (FirewallAPI.dll), which occurs when the library is blocked on an advanced local procedure call (ALPC) port while attempting to diagnose a connection failure and retrieve information. Cluster Sets: A couple of key functionalities to enable end-to-end testing of Cluster Sets scenarios are not present in this build, so defer all evaluation of this scenario to a future build. Bugcheck during volume creation: A stop error may occur during volume creation in a cluster. The recommended workaround is, after restarting the computer, to delete the volume and try creation again. Bugcheck during volume repair: A stop error may occur during volume repair in a cluster. The recommended workaround is to restart the computer. No corruption or data loss is expected.

The Dependency Service or Group Failed To Start

Le 11 août 2017, 04:10 dans Humeurs 0

Now this is a frustrating printer spooler error that a lot of Windows users have been pulling their hair out over. We are going to attempt to solve your "error 1068" (or the similar "error 1075") problem right now.

Error 1068 (or 1075) Printer Spool Problem

When you try to start the Print Spooler service (using Windows Services.msc), you receive and error message like one below and the service fails to start:

Could not start the Print Spooler service on Local Computer.

Error 1075: The dependency service does not exist or has been marked for deletion.

Could not start the Print Spooler service on Local Computer.

Error 1068: The dependency service or group failed to start.

If you check your event log files, you might noticed the following messages as well:

Event ID: 7003

Description: The Print Spooler service depends on the following nonexistent service.

Event ID: 7001

Description: The Fax service depends on the Print Spooler service which failed to start because of the following error: The dependency service does not exist or has been marked for deletion.

Solutions For Printer Spool Errors

How to fix BAD_SYSTEM_CONFIG_INFO in Windows 10

Le 9 août 2017, 10:26 dans Humeurs 0

Among the many problems encountered on Windows 10, the most serious error is the Blue Screen of Death which is also known as STOP errors. The reason for the occurrence of such errors is generally incorrect system settings or a faulty hardware. In this tutorial, we are going to discuss bad system config info windows 10.

How to Fix BAD_SYSTEM_CONFIG_INFO in Windows 10

Since these errors can pose great problems, in this article we will help you on how to fix BAD_SYSTEM_CONFIG_INFO error on windows 10.

Let's begin the methods to solve this error completely:

METHOD 1: Updating the drivers of the system:

It is advised to update and remove all the outdated and incompatible drivers on your system as they can cause many problems such as, if your drivers are outdated, then you will not be able to use certain hardware and get an error such as bad_system_config_info. So, in order to avoid BAD_SYSTEM_CONFIG_INFO errors, you have to be sure that all your major components in the system are up to date with latest drivers available.

Downloading drivers for the system is not a very complex method. All you have to do is visit the website of your hardware manufacturer, search for your device and download the latest drivers that are available for it. You should remember that you have to update as many drivers as possible to successfully fix this problem.

METHOD 2: Using the bcdedit command:

Having incorrect system configuration can also be the reason for the occurrence of the BAD_SYSTEM_CONFIG_INFO error. This error will be caused if your system configuration is not proper, and the number of processors and amount of memory occupied in the configuration file doesn't match the correct value. This BAD_SYSTEM_CONFIG_INFO error can even prevent your access to Windows 10 entirely. But you can easily solve this problem by following the given steps:

Restart the system at the time of the reboot. You need to repeat this step till you get to the Automatic Repair. Once in the Automatic Repair, choose the option to Troubleshoot. Under this go for the Advanced Options and then go to Command Prompt. Now type the following commands in the command prompt window that appears bcdedit/deletevalue {default} numproc bcdedit/deletevalue {default} truncatememory Method 3: Fixing the BCD file:

BAD_SYSTEM_CONFIG_INFO error can also be caused if the BCD file on your system gets corrupted or damaged and in this case, you will not be able to access Windows 10 at all not even in Safe Mode. To solve this problem you need to have a Windows 10 installation DVD or a bootable USB flash drive containing Windows 10 in it. Now, to fix the damaged BCD file, you need to perform the following steps:

Boot your system by inserting the bootable DVD or USB flash drive. When the Windows 10 setup starts, click Next option and then choose the option Repair your computer. Now choose Troubleshoot. Under this go for the Advanced Options and then go to Command Prompt. Now type the following commands in the command prompt window that appears. Do not forget to press ENTER after each command bootrec/repairbcd bootrec/osscan bootrec/repairmbr The last command here will delete the Master boot records and will recreate them as well. After the successful implementation of the commands restarts your system.

METHOD 4: Fixing the Windows Registry:

There might be certain registry issues that can lead to the appearance of BAD_SYSTEM_CONFIG_INFO error. To repair the Windows registry perform the given steps:

Boot your computer using Windows 10 installation media as mention above. Now choose Troubleshoot. Under this go for the Advanced Options and then go to Command Prompt. Now type the following commands in the command prompt window that appears. Do not forget to press ENTER after each command CD C:WindowsSystem32config ren C:WindowsSystem32configDEFAULT DEFAULT.old ren C:WindowsSystem32configSAM SAM.old ren C:WindowsSystem32configSECURITY SECURITY.old ren C:WindowsSystem32configSOFTWARE SOFTWARE.old ren C:WindowsSystem32configSYSTEM SYSTEM.old This will rename all these files and you won't be able to use them after you rename them. Now enter the following commands in the Command Prompt: copy C:WindowsSystem32configRegBackDEFAULT C:WindowsSystem32config copy C:WindowsSystem32configRegBackSAM C:WindowsSystem32config copy C:WindowsSystem32configRegBackSECURITY C:WindowsSystem32config copy C:WindowsSystem32configRegBackSYSTEM C:WindowsSystem32config copy C:WindowsSystem32configRegBackSOFTWARE C:WindowsSystem32config This will copy the registry files back and replace them with the old files. Now, close the command prompt and restart the system.

METHOD 5: Performing System Restore:

If the previous methods did not solve the problem they you can try System Restore of the system. To solve using System Restore performs the following steps:

Restart the system at the time of the reboot. You need to repeat this step till you get to the Automatic Repair. Once in the Automatic Repair, choose the option to Troubleshoot. Under this go for the Advanced Options and then go to System Restore. Now enter your username and follow the instructions that are provided. Choose your restore point according to your wish and click on Next option. Now, wait until the System Restore finishes. If your problem didn't get solved by System Restore, then try to perform the Windows 10 reset. But remember to create a backup before the reset because resetting the system will delete all files from your system. Perform the following steps to reset the system:

Restart the system at the time of the reboot. You need to repeat this step till you get to the Automatic Repair. Once in the Automatic Repair, choose the option to Troubleshoot. Under this choose the Reset this PC option. Now select Remove everything and then choose the only the drive where Windows is installed option. Now select the Just remove my files option. Finally, click on the Reset button and wait for the process to complete. METHOD 6: Checking for hardware issues:

In many cases, it is observed that BAD_SYSTEM_CONFIG_INFO error is caused by the presence of faulty RAM. So, it is advised that you check the RAM in your system. This problem can be sorted if you replace the faulty hard drive. You should keep in mind that you have a detailed inspection of your hardware in the system as this problem can be caused by any damaged component of the system.

Voir la suite ≫