Share via

Is VS Enterprise 18.3.2 update a problematic ?

Jignesh Desai 151 Reputation points
2026-02-27T10:57:28.81+00:00

Hi,

Yesterday I had successfully build and published MAUI Blazor Hybrid App successfully with VS.NET 2026 Version 18.3.1. Today I found new update 18.3.2 and thought to update VS before starting the day.

But as soon as i trying to compile the app I started getting error one by one

Issue #1
<PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)" />

<PackageReference Include="Microsoft.Maui.Controls.Compatibility" Version="$(MauiVersion)" />

<PackageReference Include="Microsoft.AspNetCore.Components.WebView.Maui" Version="$(MauiVersion)" />

AI says : The $(MauiVersion) MSBuild property was previously provided by the MAUI workload, but the VS 18.3.2 update no longer sets it, so these resolve to empty — causing the NU1015 error. The fix is to replace $(MauiVersion) with explicit version numbers, matching the Microsoft.Maui.Core version (10.0.30) already on line 165.

and serious one issues followed.
The NU1015 error is fixed. Now there's a new error from the Windows App SDK — WindowsPackageType defaults to None in the newer SDK, conflicting with GenerateAppxPackageOnBuild=true. I need to explicitly set WindowsPackageType to MSIX in the Windows property group.

Progress — the MSIX error is fixed. Now the newer Windows App SDK requires explicit platform specification. Let me add RuntimeIdentifiers to the Windows property group:

The RuntimeIdentifiers (plural) lists available RIDs but doesn't select one for the current build. The real culprit is GenerateAppxPackageOnBuild=true — it forces MSIX packaging on every build, and the newer Windows App SDK 1.7 now strictly requires a specific architecture for that. Let me revert the RuntimeIdentifiers and instead disable package-on-build (you can still publish MSIX explicitly):

The WindowsPackageType=MSIX setting itself triggers the neutral-architecture check even without package generation. Since GenerateAppxPackageOnBuild is now false, we don't need to force WindowsPackageType=MSIX either. Let me remove it:

The build logs show "Deploy failed" with zero detail about why. This is an Android deployment issue, not a compile issue. Let me check the Android environment state.

Found the issue — no Android device or emulator is connected. adb devices returns an empty list. Let me check if Windows Subsystem for Android (WSA) is running, since your project comments reference it.

I am not sure what is happening... I am numb. I am just simply trying to run/debug on .net10 windows. Android is not in picture at all for now.

and finally this error..
User's image

I also need to know if someone can guide me how to revert back to previous VS.NET update

Developer technologies | Visual Studio | Debugging
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adiba Khan 2,265 Reputation points Microsoft External Staff
    2026-03-02T10:28:11.4933333+00:00

    Thanks for reaching out. The issue you are encountering is specifically the Nui015 , the “Msix Package” command failure and and brain deployment loop are known regressions affecting MAUI blazor hybrid projects in this specific build.

    Below are the official guidance and technical resolution for each issue.

    1. Resolving the NU1015 error ($(Maui Version) missing) In version 18.3.3, the $(Maui Version) MSbuild The party is no longer automatically populated by the MAUI workload. This results in the property resolving to an empty string breaking your NuGet package references.
      1. Officially fix: manually specify the version number in your .csproj file
      2. action: locate your <PackageReference> tags and update them as follows: 
              <PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)"/>
      <PackageReference Include="Microsoft.Maui.Controls" Version="10.0.30" />
    2. **Fixing **** ****“MsixPackage” **** **Command and Profile Errors The error “the project does not know how to run the profile.… command ‘Msix Package’” Occurs because the newer windows app SDK 1.7 plus defaults windowspackageType to none which conflicts with GenerateAppxPackageOnBuild = true.
      1. Option A (Recommended for Debugging) Disable automatic package generation  to allow the “windows machine” target to run normally In you .csproj, set: 
              <GenerateAppxPackageOnBuild>false</GenerateAppxPackageOnBuild>
      2. Option B (for packaging): if you must build an MSIX, you must explicitly define the package type in your Windows-specific PropertyGroup: 
              <WindowsPackageType>MSIX</WindowsPackageType>
      3. Reference: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/release-notes/windows-app-sdk-1-7?pivots=stable
    3. Stopping” Android Deployment” on Windows targets If the build logs show “deploy failed” for Android while you are targeting windows, the IDE is incorrectly attempting to initialize the Android environment (ADB).
      1. Workaround: Ensure your Solution Platforms (next to start button) is set to x64 or arm64 instead of Any CPU as “ Any CPU” can trigger multi-platform deployment checks that fail if no emulator is present.
      2. Check : verify the your launchSettings.json (found in the Properties folder) does not have a rogue Android profile set as the default.
    4. How to revert to version 18.3.1 If these manual fixes do not resolve your workflow issues, we recommend rolling back to the stable 18.3.1 build.
      1. Open the visual studio installer
      2. Click the more dropdown next to your VS 2026 Enterprise instance.
      3. Select Rollback to previous version. This will restore version 18.3.1.
      4. Reference:https://learn.microsoft.com/en-us/visualstudio/releases/2026/release-history

    Next Steps

    To ensure the fix is applied correctly, please perform a Clean Solution and delete the bin and obj folders after editing your .csproj.

    Please let us know if you require any further assistance we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer".

     

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.