Tag: video

Posted on by

Guide to Fixing the “Black Screen After Windows 10 Logo” Issue (Cause: Video Driver)

This problem is often caused by an incorrect or incompatible video card driver (typically an automatic update installed by Windows Update). The solution is to disable the problematic driver by entering Safe Mode.

PHASE 1: Access the Recovery Environment and Force Safe Mode

Since the PC freezes before the desktop, you must use the Windows Recovery Environment (WinRE) to access the system.

  1. Force the Recovery Environment: Turn the PC on and, as soon as you see the manufacturer’s logo or the Windows loading circle, force a shutdown by holding the power button. Repeat this process three consecutive times. On the fourth startup, the PC will display the Windows Recovery Environment (WinRE).
  2. Access the Command Prompt: From the blue WinRE menu, follow the path:
    • Troubleshoot (Risoluzione dei problemi)
    • Advanced options (Opzioni avanzate)
    • Command Prompt (Prompt dei comandi)
  3. Force Safe Mode Startup: When the Command Prompt opens (likely on the temporary X: drive), type the following command and press Enter:

     

    bcdedit /set {default} safeboot minimal

    (Verify the confirmation: “The operation completed successfully”)

  4. Restart: Type exit and, from the recovery options screen, select “Continue and exit to Windows 10” (or similar text). The PC will restart into Safe Mode.

PHASE 2: Remove the Problematic Driver and Restart the System

Once in Safe Mode, the system is stable because it uses a basic video driver.

  1. Uninstall the Video Driver:
    • Right-click the Start button and select “Device Manager” (Gestione dispositivi).
    • Expand the “Display adapters” (Schede video) section.
    • Right-click the device and select “Uninstall device” (Disinstalla dispositivo).
    • CRUCIAL: Check the box “Delete the driver software for this device” and confirm the uninstallation.
  2. Disable Safe Mode Force: Reopen the Command Prompt as Administrator  and type the following command to restore normal startup: 
    bcdedit /deletevalue {default} safeboot
  3. Functional Restart: Restart the computer. Windows should now start normally, using the generic basic display driver.

PHASE 3: Install the Correct Driver and Create Checkpoints

The PC is stable but unoptimized. Before installing the driver, it’s essential to create a safety checkpoint.

  1. Create a Security Restore Point: Search for create a restore point  in the Start menu and create a manual restore point (name it, for example, “Stable Pre-Driver State”).
  2. Install the Certified Driver: Download and install the version of the driver certified by the manufacturer for your specific model (avoid generic drivers from the video card manufacturer or Windows Update).
  3. Create a Second Restore Point: After installation, and after verifying the PC works correctly, create a second restore point (“Functional Driver”).

PHASE 4: Future Problem Prevention (Blocking Windows Update)

To prevent Windows from overwriting your functional driver with the problematic one:

  1. Pause Updates: Pause Windows updates for seven days through Windows Update settings.
  2. Hide Unwanted Updates: Use the official Microsoft tool “Show or hide updates” (wushowhide.diagcab) (downloadable online). Run the tool and select the specific video driver update (the newer version) that you believe is causing the issue to hide it permanently from Windows Update.
  3. Resume Updates: Reset the update search settings in Windows Update.

The Safety Net:

If, while trying to solve the new driver issue, Windows Update manages to install the wrong driver and the PC returns to the black screen:

  • Force the Recovery Environment (by turning the PC off and on 3 times).
  • Access System Restore and roll back to the “Functional Driver” restore point. This will quickly revert the PC to a stable state, resolving the issue in minutes.
Posted on by

Authentication Developing for Azure Media Service

After creation of your Azure Media Service (AMS) Account (Create a Media Services account using the Azure portal) you need to authenticate your application that your are developing , to manage your video and streaming channels.

Developing with .net

In this article we are using .net framework to develop an app, but the information should be valid for all languages.

To develop an application with .net frameeork, you need to install, via nuget , the package windowsazure.mediaservices.extensions with its derived packages.

You can authenticate in one of two ways :

User authentication

Authenticates a person who is using the app to interact with Azure Media Services resources. The interactive application should first prompt the user for credentials.

For this authentication your app needs two strings :

Azure AD tenant  (“tenant” in example) :  In Azure portal, select your AMS and  select, on the left menu, api page. In the table at the bottom of the page one of the fields is “Domain Tenant ADD”.

Endpoint API REST (“endpoint” in example) : you can read this information directly in main page of your AMS on the right at the top of the page. Should be something like this :

https://yourams.restv2.yourlocation.media.azure.net/api/

In your application you have to write this code :

var tokenCredentials = new AzureAdTokenCredentials(tenant, AzureEnvironments.AzureCloudEnvironment);
var tokenProvider = new AzureAdTokenProvider(tokenCredentials);
_context = new CloudMediaContext(new Uri(endpoint), tokenProvider);

Running the application you should automatically see the Microsoft user credentials form

 

Service principal authentication

Authenticates a service, a specific app, without user interaction. To use this authenticaton in your app, you need four strings :

Azure AD tenant  (“tenant” in example) : As above

Endpoint API REST (“endpoint” in example) : As above

Client ID (“clientid” in example) : Enter in azure portal and look for “applications”. Add new application. After creation, in properties, at the top of the page, you can find the “application ID”.

Client Secret (“secretid” in example): in your AMS select the API page. In the middle of page you can find a little form with two fields. In the first field you ha to select the application created before. Use the second field to create the client secret.

In your application you have to write this code :

AzureAdTokenCredentials tokenCredentials =
new AzureAdTokenCredentials(tenant,
new AzureAdClientSymmetricKey(_clientid, _secreteid),
AzureEnvironments.AzureCloudEnvironment);

var tokenProvider = new AzureAdTokenProvider(tokenCredentials);

_context = new CloudMediaContext(new Uri(endpoint), tokenProvider);