-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can't Patch x86 EDGE #1
Comments
@Blaukovitch anyway to ask the author of the patch? i cant ask in the forum -you know what forum- because it does not let me to make account there. |
@darkalexis1990, i see, that file is not accessible at you |
@Blaukovitch this is as far as i get with the x64: then i copy that dll and i get this error dont know what else to do,by the way the x64 125 version from the crack lab pa site that only works i cant reach the site it does not let me to complete the registration it nevers sends the confirmation mail. now for the x86 version all the steps are completed success but when i doule click the edge.exe it does not open anything even with the no sanbox commmand. in the task manager it shows the procedure. cam you kindly when you have the time to try to patch by yourself to see what im doing wrong? thanks!. @Blaukovitch when you patch and have results please tell me.maybe im doing something wrong and i dont see it. |
@Stepman123 , @natsui-river have you tried to patch with success ? |
@Blaukovitch after discusiion on the MDL forum someone had the idea to use the pached api dll's from the edge 125 windows 7 repo that is already patched and IT WORKED. that guy also tested 126 and also worked.the thing is that with the Edge Stable 127.0.2651.74 the patched does not work anymore, cause the API dllls needs again patching. can you please patch/update your api dlls so we can test with 127? thanks youre the best!!! looking for news from you. |
Hello, I copied some files from GOOGLE_CHROME_WINDOWS_7_CRACK to the Edge directory because after I applied the patch I noticed that kernel64.dll was missing. |
Hi!
Some errors? |
first of all i dont have access on https://cracklab.team/index.php?threads/1037/page-8#post-14319 second ,im trying to patch the X86 EDGE because i need that version,cause i have an old machine that only works with 32bit OS so i need the pacthed edge x86 there to use it.. all the procedure of paching is making at a x64 win7 machine VM full updated! i dont have 109 installed there!!! so i took all the API-MS from your latest chrome x86 release -> 127.0.6533.73_x86_Windows7 and i put them on the API-MS/X86 on the edge patcher .i delete the x64 folder from the API-MS in the edge patcher. im using the command -> i tried the -all also (without space between the '-' and 'all' ) i always run cmd with admin rights! the procedure completes without errors (when i copy the application folder from win11 to 7 i always edit the folder and give permissions uncheck read only etc) i do the steps and this is i get -> maybe it needs the KERNEL32.DLL. youre saying that there- > #1 (comment) and where i can find this? can you provide it me? if you want the debug logs tell me how to find them so i can show it here. @Blaukovitch |
@darkalexis1990, i thinks that after Google adds new anti-windows7 tricks, need more research. |
@Blaukovitch can you find a workaround for x86 to be patched? maybe if you dig you into the 125 edge x86 repo? so it makes clear that noone tested the edge patcher for the x86 versions :( |
@Blaukovitch if you find anything from the research tell me thanks |
@Blaukovitch i told you so many times that here youre watched by the companies thats why the new anti 7 tricks/ thats why i told you to come on the forum but you keep avoiding me anyway... |
@darkalexis1990 I don't think MDL is safe place eather Look what happened with VxKeX: https://msfn.org/board/topic/186333-vxkex-extended-kernel-project-dissapeared/page/6/ The project disappeared from github (also the user, and it was not DMCA), and the user was mysteriously banned on MDL (nobody knows why) |
@darkalexis1990, sorry! I have a lot of work to do on my main projects, so I can't afford to develop Chrome Windows 7 and everything related to it separately right now. I've started to notice that the HUGE memory problem is increasing from version to version and needs to be addressed, but I'm running out of time. I think that until the project gets a large number of stars again, it will exist for quite a long time (probably). @veso266, I still have VkHex sources, but not the most current version. I can post it for now. |
original copy: |
@Blaukovitch Thats great A big problem I see with all this projects its, that instead of having to focus to make something good in ur free time If a project is realy popular like VxKex was, its at risk for being shutdown, but a lot of people work on it, which means it progresses But if a project is not popular, it probably won't get shutdown but is dependend on one or 2 persons working on it, which means that it can get stail rather quickly and its never developed any further So sometimes I realy don't know what to wish for I realy hope people will pick up VxKex again, because its the best windows extension we got (I mean if M$ was smart they would develop this themself for money (better then any extended update support they used to offer) and charge corporations that don't want to change 😄 ) but we will see, I guess VxKex needs to find a good place to exist on without worying about being shutdown |
ok man thanks for your work. |
you think completely wrong. MDL is much safier. also it was a first level protection if you want: you can make your post seen if only you have account there. |
Sorry, meant msfn (because project of that nature (fix program to run on my old os) are usualy there) not MDL Always thought MDL is more for current things, not so much fixing current programs to run on past oses that were not designed for (thats msfn job), but if MDL is safe then maybe comunity should be established there |
@Blaukovitch
cant patch the x64 im getting the follow errors please help
![image](https://private-user-images.githubusercontent.com/107497874/348563039-1066b82c-d438-41c2-b4ac-3f8fabbad1cc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDE5ODgsIm5iZiI6MTcyNjE0MTY4OCwicGF0aCI6Ii8xMDc0OTc4NzQvMzQ4NTYzMDM5LTEwNjZiODJjLWQ0MzgtNDFjMi1iNGFjLTNmOGZhYmJhZDFjYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTEyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkxMlQxMTQ4MDhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yNWY1NmRmNTA0Y2QzOWEwY2FjYmQ4NDgwYTA5OTNlNGM4YjFhMTM1YmJhNTRhYmZmYzc3MmE2ZjY2MTIyMmU2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.hJB3irFFUdllrgWrmYezmqV-p4Grwi2MN6WhZ3mfIZY)
The text was updated successfully, but these errors were encountered: