Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could you create a 5.551.6455.0 version? #19

Open
Rplanasr opened this issue Mar 4, 2024 · 11 comments
Open

Could you create a 5.551.6455.0 version? #19

Rplanasr opened this issue Mar 4, 2024 · 11 comments

Comments

@Rplanasr
Copy link

Rplanasr commented Mar 4, 2024

Hi sl4v3k,

Could you create a 5.551.6455.0 version please?

Thanks & regards

@Rplanasr
Copy link
Author

Rplanasr commented Mar 4, 2024

sorry now is 5.560.6524.0, Apparently, the app forces the update as soon as it's accessed

@leden1
Copy link

leden1 commented Mar 4, 2024

Just download old version that has bypass from here
download.shapr3d.com/windows/Shapr3D.Package_5.540.6360.0_Test/Shapr3D.Package_5.540.6360.0_x64_ARM64.msixbundle

@Rplanasr
Copy link
Author

Rplanasr commented Mar 5, 2024

I downloaded and installed the version indicated above, I ran the program shapr and applied the patch Shapr3D-inmemory-patcher-2 but it doesn't seems to work, it still asks to apply for a trial or pay for the service.
¿any suggestions?

@sl4v3k
Copy link
Owner

sl4v3k commented Mar 5, 2024

run it from command line elevated to Admin, and see what patcher is saying on console output

@leden1
Copy link

leden1 commented Mar 5, 2024

I posted link for that version because I know it works, at least it works for me.
It is possible that he never gets fully into program because old installation left some files that get checked during startup.

@Rplanasr
Copy link
Author

Rplanasr commented Mar 5, 2024

run it as Admin says:
Shapr found!
00007ff693980000
Shapr3D.dll base addr -> 00007ff8e9b80000
WriteProcessMemory success! -> 00000005 bytes written.

But the app acting as if nothing happened

I'll try on another clean PC
Thank you for your time and answers

@Rplanasr
Copy link
Author

Rplanasr commented Mar 5, 2024

On another PC it worked.
Thanks a lot!!
The previous installation with the last version, must have left something on the disk anticipating this, because I cleaned up the registries after uninstalling it

@Rplanasr
Copy link
Author

Rplanasr commented Mar 6, 2024

Excellent contribution from you, is it possible to have a permanent solution and not in memory?

@sl4v3k
Copy link
Owner

sl4v3k commented Mar 6, 2024

Inmemory patching is sort of solution for Microsoft Store binaries. They are havely protected on disk. to make permanent patch of such binary it is necessary to switch off first all those protetcions. In order to avoid system modification and lowering its security inmemory patching is good option. So yes its possible.

@Rplanasr
Copy link
Author

Hi sl4v3k, It's just a question. I'm thinking of migrating to Windows 11, but my question is... Will Inmemory patching continue to work as it does in Windows 10?

Thanks & regards.

@sl4v3k
Copy link
Owner

sl4v3k commented Mar 30, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants