[Samsung Galaxy S21 Ultra] obrobrio2000:
It's not my first priority because I personally don't use Bixby but as soon as I have some time I'll look into it :)

Delete the .bat file in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp :)

If you downloaded from GitHub as a ZIP archive you need to extract it with something like 7zip, winzip, winrar etc.

If you mean the Quick Share app it's not my fault (probably Samsung needs those permissions to make the app work), but if you mean my script you can analyze what's in it on GitHub or by opening it with Notepad. Nothing shady :)

Hello everyone, friends! First of all, sorry for this long wait but I am a full time university student who should graduate this year and therefore I am very busy with the exams of the last year and with the composition of my degree thesis. This is a project that was initially intended only for me but which I then decided to share with you all (knowing that sooner or later Samsung would put an end to our party). For this reason, it is a project that I carry on when I have free time and, for the aforementioned reasons, I have not had the opportunity to look at it until now. I update you with the news (spoiler: negative news):

1) The old version that I had hosted on my Mega is obsolete. Samsung has decided to remove the Samsung account login from within the app and has created a separate app ("Samsung Account" on the Microsoft Store, downloadable apparently on all PCs, probably because there are apps like Galaxy Buds, Samsung Notes, Samsung Gallery etc. which are compatible with all PCs and therefore need that framework). This old version of Quick Share, therefore, at login will say that the app is too old. Even if you skip the login, the app still does not work, it does not detect any phone/tablet (probably ue to dan Android Quick Share update it now prevents the phone from being detectable by Quick Share Windows if the version of the latter is too old). I believe that the only way to partially continue to use this version is to disable automatic updates on the Galaxy Store, but the problem with keeping old versions is that in the long run you will lose important new features. Also, even if you disable updates, Quick Share (and system apps in general) will update when you do a firmware update; therefore, there is no real way to escape from updates.

2) I tried with the latest version from the Microsoft Store. This version manages to detect devices but manages to transfer a file once every Pope's death (it's an Italian saying to say that it works once in a hundred, if all goes well). Also, to make it partially work you have to unpair your phone and PC in the bluetooth settings and make them pair again by transferring a file, but even in this case it works occasionally. The problem is that if you use Quick Share you will surely also use Microsoft's handy Phone Link feature (formerly Your Phone) to complete your ecosystem. Well, Phone Link will ask you to pair devices to make calls, but this pairing will break Quick Share, making it never work again (it will always tell you "Failed").

3) I have tried with model numbers of different Galaxy Books, even one with the exact same characteristics as my PC, but after a few PC-to-phone transfer attempts it will ask to update the PC's Bluetooth drivers with the Samsung Update tool (which, unfortunately, does not show updates on non-Samsung PC, even with the registry hack). My drivers are up to date, latest version from Intel, but nothing to do.

4) In the latest versions of Quick Share Windows there seems to be Link Sharing. I tried to use it to send a .jpg file and when I open the link on the phone it says in red that the file hasn't been uploaded yet (and it will be like this forever). I then tried again with a .heic file and it uploaded successfully. In short, even the Link Sharing feature seems to be hit or miss, just like Quick Share. Even looking at the Quick Share logs, very little can be understood to be honest :(

5) Reading the reviews on the Microsoft Store it seems that these same problems are also encountered by users who own a Galaxy Book. So it makes me think that Quick Share is already a hit or miss on its own, and everything is made worse by the fact that we are using it on incompatible PCs, with different drivers, different specs etc.

6) I don't have the ability to reverse engineer the app and possibly modify it, if that's possible. But I think it would still be useless. My registry workaround was an almost random discovery while I was fumbling with Process Monitor to see which registry keys it was going to check, but if there is something inside the app code that I can't detect with Process Monitor I just don't know how to move :(

And now, what do we do?

If you have the patience to try and try to transfer a file until it works, fine, but it's impractical to have an app that works once in every hundred. Our hope is Google, which will bring Nearby Share to Windows later this year. The problem is that they said it will work on certain new PCs which will be "Fast Pair compatible". I don't know what it is, I hope not something hardware, otherwise again we are screwed.

I'm so sorry friends, within the limits of my abilities I have tried all sorts of ways but I can't understand why the transfer works occasionally. Also, on the Store page they talk about driver versions that do not match Intel's, so my guess is that Galaxy Books have OEM-customized drivers that contain things that generic Intel (or other OEMs like Lenovo) drivers don't have.

Anyway, I read your answers here on XDA and came across this answer from this user who seems to have solved every problem by replacing his wireless card. If the user confirms that everything works perfectly (PC-phone, phone-PC) and always works (not occasionally), then that could be a good workaround. I mean, better to spend £27 for a wireless card than £1000+ for a Galaxy Book. But you must have a laptop that allows you to replace the wireless card. My laptop, for example, doesn't allow me to do it :( Check it out: