alovchin91.bsky.social
Software engineer.
Rust, Kotlin, C#, .NET, Windows Arm64.
The Catfather. Coffee enthusiast.
Opinions are my own. 🇳🇱
33 posts
17 followers
15 following
Regular Contributor
Conversation Starter
comment in response to
post
Refreshing to see someone from the tech circles talk about the political situation. I’ve got a feeling that we, the IT crowd, have become too comfortable with our lives. We must wake up and begin speaking up if we don’t want to lose our free Europe.
comment in response to
post
It’s 100% in our hands to not let them to
comment in response to
post
Man, I’ve never been to Canada but I already love it there 😍
comment in response to
post
I would usually write a simple C++ or Rust app that would directly call CreateFile with these paths, to see if it’s the API or something in between that’s misbehaving 🤔
comment in response to
post
It’s also weird that with LongPathsEnabled=1 it fails without the prefix.
comment in response to
post
\\?\ should always work, regardless of the registry key. You might want to check what that native library does; maybe it strips the \\?\ prefix?
comment in response to
post
Yep, but it gets randomly loaded back again 😆
comment in response to
post
That’s funny, I get exactly the opposite experience 😆 Maybe that’s because my extension is a DLL surrogate-based InProc server. There’s no way to control when Explorer unloads it, so even after unregistering it, it’s not guaranteed to be released. With MSIX it gets released right away.
comment in response to
post
I don’t know what was the idea behind it, but probably they could control those packaged extensions more easily. For example, you’ll have quite a hard time refreshing the context menu after registering and unregistering extensions via the registry, while package changes are picked up immediately.
comment in response to
post
Oh! I was wondering why this option was there but did nothing. Gonna check it out!
comment in response to
post
The thing is, Microsoft’s own extensions do not always support Arm64 🤷♂️ Like UWP .NET 9 project templates (!), for example.
comment in response to
post
Sure thing, but I mean at least one can boot these new machines from an ISO, at least according to this page:
learn.microsoft.com/en-gb/window...
SPX needed drivers injected into boot.wim afaik
comment in response to
post
Well at least with these new devices it seems one doesn’t need to inject drivers anymore as stock ISOs are supposed to work just fine. So perhaps it’s still a worthy upgrade from my SPX after all 😂
comment in response to
post
I have a feeling that the restore image is botched for SP11, because this is the only difference — I’ve restored this dude (twice 🤦♂️) because of other issues.
comment in response to
post
Yup. The story is in fact much more fun, because a few days ago I’ve casually upgraded another Surface Pro 11 without issue.
This one — I’ve spent an hour on the phone with a Microsoft Support rep, and we’ve tried a number of things. Literally nothing worked. In-place upgrade was the last resort.
comment in response to
post
Finally I can secede from TwiX! 😅 Welcome!
comment in response to
post
Hope is all we got
comment in response to
post
Pure randomness, huh? 😏 I sure hope for some Arm server randomness…