Pow3r.us3r.78

The Windows 11 I have is pretty much useless. It didn't install a lot of necessary apps, including the Windows store. And if I try to add the AppX package manually, it says:

Attempting to register package: Microsoft.WindowsStore_12104.1001.113.0_neutral_~_8wekyb3d8bbwe Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Validatie van updates, afhankelijkheid of conflict voor h et pakket is mislukt. In Windows kan pakket Microsoft.WindowsStore_12104.1001.1.0_arm__8wekyb3d8bbwe niet worden geïnstalleerd omdat dit pakk et afhankelijk is van een framework dat niet kan worden gevonden. Geef het framework 'Microsoft.NET.Native.Framework.2. 2' dat is gepubliceerd door 'CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US', met neu trale of ARM-processorarchitectuur en minimale versie 2.2.29512.0, samen met dit pakket dat moet worden geïnstalleerd.

(sorry for the Dutch).

Apparently I cannot install the Windows Store because some .NET framework version is missing. Sweet. Back to square one. Two days wasted and I probably need to revert to Windows 10 in the end.

I understand your point, but that is still not going to change the fact that we did drop 32-bit support, and will not revert the decision.

I never asked for that.

Did you get a chance to launch Remote Desktop Manager x64 on your Surface Pro X running Windows 11 yet? That is what truly matters here: fixing your issue.

I have it running. Dashboard looks horrible (due to scaling issues) but it works.

Start-up time hasn't improved either (still 44s of freezing my entire laptop just starting up the application, followed by 15s to get the data source up).

... even then, we did so after Microsoft finally made 64-bit Intel emulation available in a stable Windows release, Windows 11

Except that Microsoft didn't release Windows 11 to ARM pc's yet (and apparently for good reason, given my installation troubles).

From my perspective this has been a stapling of different choices where only the combination is really problematic:

• A new RDM version dropping 32-bit support

• A database upgrade preventing the use of previous versions

• Microsoft not yet offering x64 emulation for arm64

The first two were made by Devolutions. Apparently you missed the third one, thinking Windows 11 was available for arm64 and would make the first two decisions ok.

Combining dropping 32-bit support with a database upgrade locking out previous builds, you took a risk. You blocked off a 'way out', apparently not even realizing that as you suggested me to use 'a previous build'.

If you would have not dropped 32-bit support, I would have been fine. If you would not have compounded that with a database upgrade preventing earlier builds from connecting, I would have been fine. And if you would have known that Windows 11 was not yet available for arm64, you would probably not have made the first two decisions.

I don't have any problems with mistakes being made. No mistakes means no progress. The only thing I have a problem with is framing it as 'microsoft has dropped the ball'. If you don't own up to the consequences of your own decisions, how are you ever going to improve?

Let's just say that Microsoft dropped the ball on this one

I see this differently. The different scale on which Microsoft operates means you will have to follow them, not the other way around. You didn't need to drop 32-bit support right now but you chose to do so. In my opinion prematurely. You could have waited for Windows 11 to become mainstream available to arm64.

In the meantime, you can keep using the previous RDM builds.

As I explained earlier, that's no use. The database is upgraded and previous builds no longer have access.

Someone suggested to me using the PC Health Check app to trigger the upgrade to Windows 11. This is the tool you normally use to check if your PC can be upgraded to Windows 11, but apparently there's a way to use it to initiate the Windows 11 upgrade.

Yes, I used that before. I gives the green light but doesn't offer to initiate the upgrade for arm64 machines, only x64.

I've managed to upgrade to Window 11. After some research on the error code it seemed to be related to connected hardware and, lo and behold, by removing my Logitech USB mouse I was able to upgrade.

Running Windows 11 on Surface Pro X now. I'll try and get RDM to run next.

Pfff. Windows 11 is not playing nice. Already wasted most of my day on this :(

Was it really, really necessary to drop x86 support a few months before Microsoft would offer a normal upgrade to Windows 11 for Surface X (and other ARM PC's)?

I mean, you don't support my iPhone (because of 2 factor Azure SQL) and now you don't support my laptop either...

Not happy.

I think that's the one. Can you tell me how exactly the Windows 11 Update Assistant fails? My understanding is it won't run at all because it's a 64-bit intel binary, is that correct?

Yes. See attached (sorry for the Dutch but it should be clear enough).

I upgraded to Windows 11 using the Insider Preview channel builds, but if you're looking for the Windows 11 ARM64 ISO, Microsoft doesn't provide one, but you can use uupdump.net to create your own using the files available from the Microsoft CDN.

This the one I want?

Upgrade to Windows 11 (22000.258) arm64 arm64 2021-10-12 17:05:19 UTC 24b475a3-b2b0-4464-82d1-2dd0d4a9eed8

Are you saying that the Windows 11 Update Assistant does not support Windows on ARM?

Yes, x64 only :(

ISO image is also only x64. Download on MSDN also only x64. I don't think there's a way to get Windows 11 RTM for arm64 yet?

Can't use the Installation Assistant or the Media Creation Tool either because those don't support ARM64 :(

It's not offering a Windows 11 (Pro) upgrade to me. Is that a preview you're running?

Just tried a clean install but that doesn't work either.

We upgraded our database version so now I need RDM 2021.2.0.0 or later. If I try to upgrade, however, I get the message 'Remote Desktop Manager cannot be installed on 32-bit Windows versions.'.

As you don't have an arm64 build for RDM, I need to use the 32-bit version, but apparently you discontinued support for 32-bit with 2021.2.x.

I am currently running 2021.1.44.0 which is working fine on my Surface X (ARM) in 32-bit mode but can no longer connect to my database :(.

Any ideas how to fix this?

Yes, we used that setting now, but it's hard for us to predict when it's necessary and we don't want to force users to upgrade every time either. It took me a while to figure out that that was indeed the issue too, as at first it didn't appear to help...

An 'Automatic' switch as you suggest would be great.

I think from a user perspective just triggering a message that a client upgrade is necessary (after this database upgrade) would be great?

Now we panic 'everything is gone', especially because you don't see an error message but just an (almost) empty vault.

Ah, yes, found it. My apologies.

We've had two more instances of the same issue and the common occurence is that in both cases the client version was very old (as well), requiring multiple upgrades or an uninstall/reinstall. After the upgrades we needed to clean the caches before it worked. The uninstall/reinstall path works best as it is fastest to do and cleans up caches, etc, as well.

Hope this helps others!

I created a problem report from within the app but haven't heard anything yet. Problem seems to have solved itself so you can close that.

Very strange and very scary for my Vault to get 'lost' somehow but good it's back.

Ok, this is getting stranger and stranger. Now I have my User Vault back but my main vault is 'Not connected' but does show 1634 entries?

Since a few days my User Vault only contains a single entry (the newest). It used to be 100+. It is as if a whole new User Vault was created. I tried ctrl-F5 and cleared the cache but both didn't work. I'm on the latest version (2021.1.20.0)

As background: we're working with RDM on an Azure SQL database with Active Directory Interactive (MFA) login.

There have been two changes that might be the cause:

1. We've upgraded the RDM database as required by the last RDM client update

2. We've changed AAD authentication from ADFS to cloud

Is there any way to see and hopefully 're-attach' my old User Vault? Or do I need to restore a database back-up and connect to that?

Hi Bracine,

thanks for the quick answer. I'll look into these options. I could use the SQL data source for an Azure SQL as long as I have 'sql users' for authentication, right?

We just switched away from DPS so I don't really like going back to that. Maybe a devolutions online database might be an option (we used that before DPS) although I think that would still leave us without 2-factor on datasource level, right?

Just out of curiosity: what Microsoft framework are you using?

Thanks!

Hi,

in an effort to reduce our on-premises footprint we've recently switched from a Devolutions Server to Azure SQL as datasource. Unfortunately this means the iOS is no longer usable. Can you add support for Azure SQL as a datasource to iOS (with Active Directory Interactive / MFA support for authentication)?

Thanks!

:thumb:

Thanks! That was it. As soon as I clicked the License button it migrated my license to the new place.

Any way to automatically assign licenses to new users?

2019.2.16