Hi
Anyone successfully encrypted their remix os?
Mine just reboots to the os
I have the same issue, I think, when I click on Encrypt from within the Remix OS setting it just does a sort of reboot (quicker than a standard reboot, that is) and drops me back at the front pin screen.
Did you get anywhere with resolving this issue?
I am dual booting with Windows 10 (bitlocker encrypted). Both are installed on the internal SSD of my laptop. It is a GUID type partition with UEFI type BIOS.
The method I used to install (I didn't explore others as this seemed simple) was to unpack the Remix OS download from within Windows, create a FAT32 partition and copy to the new partition. I then used EasyUEFI to point at the relevant file to boot in /efi/boot.
The only other thing that I needed to do was to modify the persistant GRUB entry so that it would create a datafile, otherwise it basically ran in guest mode regardless of which option I selected.
It's been working well for a few weeks since initial install.
Thoughts or assistance would be greatly appreciated.
All the best,
Dan
Please excuse the gratuitous bump, but I would really appreciate if someone could post if they have sucessfully encrypted their Remix OS installation? And if any special steps were necessary?
Thanks
Dan
In the absence of a solution - some help in how to debug this issue would be greatly appreciated.
Sorry to bump this thread again - but has anyone successfully encrypted their Remix OS install?
Same here
Just to let you know - you're not the only ones. Currently my new RemixOS installation is failing to encrypt - I've installed it onto a USB stick and it fails both under Virtualbox and when booted directly from hardware.
From looking online for similar issues with Android in general they appear to be related to hardware settings like being connected to a wireless network, having an SD card in use, or not being in landscape - not I'm not sure how to fix this with Remix OS. Also I think all those issues refer to old versions of Android.
I'd be interested to hear if either of you fixed this problem, or on any tips on even how to get logs ( "logcat" appears to only show logs since the last boot, so isn't any use here ).
So this is an old thread, im hoping to get someone to answer these guys and my question. Can Remix OS be encrypted?
when choosing to encrypt it just does a soft reboot. im trying to use my laptop for corporate byod but the device had to be un-rooted and encryptable. so far i fixed the root but its still a no go on encryption. if not, is there an android os i can use on pc that is encryptable ?
Related
hello
I install Remix OS on my pc
Config
moderbord Asus P6TSE
Ram 24 GB
GPU GTX 960
CPU Intel® Core i7-920
i use a ssd to boot this os and freeze on boot ...
Image
http://img15.hostingpics.net/pics/339816IMG20160124171700.jpg
Checking Data Partition....
ANDROID
Click to expand...
Click to collapse
ty in advence
When you boot up press "e" to edit the boot info, place DEBUG=2 into the script after 'androidboot.hardware=remix_x86_64' so it looks like 'androidboot.hardware=remix_x86_64 DEBUG=2' hit F10 (softly)
Debug boot should begin.
Type exit when prompted, ignore any warnings that might come up concerning hardware not being picked up, type "exit" when prompted to do so to move on. After a few times typing "exit", does an error like this continue to roll up your screen: "init: Couldn't probe module 'net-pf-16-proto-5' "? :fingers-crossed:
i make a video
https://youtu.be/7tdO9nmLBmg
A quick question. Are there any other drives connected?
You could try actually install it onto your SSD from the boot up.. Your SSD would need 2 partitions though.. One is FAT32 (around 3GB large) and the other can be FAT32 or NTFS, it wont make a difference. If you want to know how to do the install from boot then just send a reply asking.
I have just tried with a different machine and I'm getting a full SELinux error. I doubt that there is anything that we would do.. (I'm not pro enough to go reading through the actual OS files... ) Not all PC's are supported unfortunately. Mine is not, I have had better luck running Remix OS in Virtual Box, well... before the latest release at least. Now I'm getting errors that seem to have been around since Android_x86 project began.
Another option would be to try the Legacy version if your motherboard is able to boot legacy. (Sorry, have not tried looking at your MoBo)
My advice (which I am also following) would be to be patient and just hold out for a while. Until the next update comes along for us to try.
More support is intended on being added with every release.
all my files is in a fat32 partitions and work on my laptop is just my pc ... wont works
Are there any other drives connected?
yes i have 4 drive with my pc
If it is working on your laptop then settle with that for now.
No, not other drives would be recommended, just saw them in the debug at the beginning.
The error that seems to be coming up for you and I (this is as far as I understand) has to do with kernel security settings as to what to allow on boot. The issue can arise when certain files have not been given the policy labels that they require to run. So they effectively get denied constantly. This is likely where a lot of the added hardware support will sort things out... I'm also running an NVidia Card.. could be the drivers needed..(although that would not explain why VM's don't work)
Sorry that I cannot help you mate.. This is going too deep into the realm that I know little about when it comes to the actual stuff. I follow instructions when having to make a change to my Linux distro.
I do envy you having the latest version working on a device. My laptop wont boot for me either.
You could try the Andriod_x86 forums and see what the common threads are. Seeing as Jide is using android_x86 as a base.
If anyone else knows more and is able to shed light on the matter, please do so? I am also up to correction on my statements.
I asked the same question on other forums and on google group
https://groups.google.com/forum/#!forum/remix-os-for-pc
http://forums.mydigitallife.info/threads/67863-Remix-OS-freeze-on-boot
gaaara said:
hello
I install Remix OS on my pc
Config
moderbord Asus P6TSE
Ram 24 GB
GPU GTX 960
CPU Intel® Core i7-920
i use a ssd to boot this os and freeze on boot ...
Image
http://img15.hostingpics.net/pics/339816IMG20160124171700.jpg
ty in advence
Click to expand...
Click to collapse
Nvidia GPUs have trouble with remix os and you wont be able to run it properly.
ty
a new version of remixos is released
https://groups.google.com/forum/#!topic/remix-os-for-pc/Tl9yTkALhN8
i test it and the os boot and loop on welcome menu ... loll i make video for skip the logo go to 1:30
https://www.youtube.com/watch?v=Cu6hF39CoJI
ty for your poste
I know its not an answer to your question, but have you tried the new 2 February version? I have got it working in VirtualBox atm.
Just as the title says, I'm curious if there exists a touch (or hardkey, i.e. volume up/down and windoes key) enabled bootloader.
Currently i have to press arrow keys and enter to select either windows or android.
Is there such a thing? It would be amazing. Id rather not have to stop at the keyboard to boot to an os from grub.
Thanks in advance!
Well .. I had suffered from this problem for longtime and finally I solved by an app called android-x86 installer it's the only way to boot from your Windows tablet without keyboard at last what I ended up with .. so yo have to download an old version I recommend the ALPHA version and install it with android-x86 installer 2.4 UEFI version after finished installing you have to download the latest version of remix OS and extract with 7zip or winrar then replace all file with the same name in folder androidOS that the direction of ALFA you already installed now You can boot with two ways either from settings/update / recovery and then press restart now at advanced startup then after reboot choose "use a device " and last thing chose android OS wait 9 seconds in grub2 an finally the remixOS will boot or by simply choose android OS from boot menu by volume Up/down
Boot solution for XPS 12 9250
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
namitutonka said:
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
Click to expand...
Click to collapse
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
HypoTurtle said:
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
Click to expand...
Click to collapse
Very excited to pursue this, but this week is filled with close family coming here to stay for our only holiday celebration. Will post back here when I get that unallocated space, after creating a backup of the current system. May use Gparted, but will check out minitool as well.
Walk through, dual boot Remix OS + Win10 on XPS 12 9250
@HypoTurtle
Waiting on a second USB-C to USB cable so I can boot a Macrium Reflect flash drive and backup a restorable PC image to an external Hard drive. After I'm sure I can restore this image I'll try to install Remix OS.
This youtube link is straightforward and simple to follow for the dual boot installation process. I've seen many reporting hardware/software issues on the many XDA forum threads branching off of "Remix OS for PC". So obviously one size does not fit all. Compiling and replacing different Linux kernels, editing grub.cfg, initrd.img, system.img, data.img.... The very worse thing on xda forums are ignorant end-user whiners like me who want instant gratification with their perfectly working phone or tablet. This vast forum has so many xda-developers, steeped in code, gaining and sharing trial and error knowledge. So many thousands of threads where xda-developers are taken for granted to lay solutions into end-user's laps. So many of us end-users are oblivious to this baby sitting. I will try the time consuming and painstaking learning curve. The least knowledgeable member on xda-forums should try to learn and not be spoon fed. It is essential, whatever our capacity, to all become developers interested in expanding the usefulness of our devices over and above the limited and constrained manufacturer's parameters.
Why another tutorial?
As I searched the net and XDA for a guide to actually install Remix OS and found nothing that worked for me I decided to share with you guys how I managed to install it in Resident Mode. Writing this from XDA Labs on my PC now... For me I found out that the Remix OS installer is totally useless - with some copying from Remix OS folder to root folder of the created partition and manually adding UEFI entry I managed it to boot in Guest Mode but Resident Mode was still not working (bootloop). This started to make me mad as I tried so many tutorials already...
So I tried Phoenix OS and it seemed at first that this one was much better - no need for adding UEFI boot entry or experiencing Windows boot entry problems and such as it installs GRUB and boots the OS just fine. First entry in GRUB is Windows, second one Phoenix OS. Well, started it and it booted up... finally! Used it, wanted to install an app and ran into a random reboot. After a while I recognized that these random reboots happened quite often and the system was unusable for me. So my idea was just to replace Phoenix OS files with Remix OS files as the booting part was already working... and guess... it worked! You can't choose Guest Mode though, but I think you won't need that at all on your PC.
Best one on this: you won't need to open your BIOS start-menu and can boot up normally, just choose your system in GRUB bootloader which appears automatically without the need to do anything before. I find it quite annoying to hit BIOS button to start Remix OS, don't you too? So if you are able to install but don't like that behaviour this tutorial is also for you!
So here it is...
On which machines does this work?
Should be working on all PCs / Laptops running Windows 10 with GPT and UEFI BIOS. Probably also works on machines with MBR instead of GPT partition table and legacy Bios, quite sure this works also on older Windows versions (7/8/8.1). Just let me know if it works for you or doesn't.
How to install
(1)
- Create an NTFS partition on which you want to install it (right, no FAT32 crap!). It should be at least 32 GB.
If you don't know how just search XDA or Google. There are several Remix OS installing tutorials on YouTube which show how to do that in Windows.
(2)
- Download Phoenix OS 1.0.9 RC
- Download Remix OS or Remix OS Hacked Edition if you like to have root and some tweaks for it.
I used Hacked Edition.
(3)
- Use Phoenix OS installer and install it on your created partition (make sure you got the correct drive letter! I'm not responsible if you don't and lose your data...), don't reboot.
- Open the created partition in Explorer.
Create a folder named RemixOS, move all files from PhoenixOS to RemixOS.
(Obviously Phoenix is based on Remix and expects it's data to be in RemixOS folder. Funny bug. ;D)
- Reboot. Choose Remix OS.
Enjoy the nice, buggy OS. For some this may be just everthing they need. If you're happy and experience no reboots or other bugs you should be just fine and don't have to follow the next steps.
(4)
- Reboot to Windows.
- Unzip Remix OS archive - should be 2 files: Remix OS image and installer. You could safely delete the installer as you won't need it.
Use 7zip or Winrar (or whatever) to extract the Remix OS image file into a folder.
- Move the contents of that extracted folder into the RemixOS folder on your created partition. Overwrite everything. You could also extract the image file directly into RemixOS folder.
(5)
- Reboot. Choose Remix OS.
- Done.
You now should be running a working Remix OS in Resident Mode. Works fine here.
Be nice and hit thanks if I could help you.
Zwulf said:
Why another tutorial?
....
(3)
- Use Phoenix OS installer and install it on your created partition (make sure you got the correct drive letter! I'm not responsible if you don't and lose your data...), don't reboot.
.....
Click to expand...
Click to collapse
Hi.
Does that mean that the installation of Phoenix OS erase all the data in that partition?
Regards.
jocaferlo said:
Hi.
Does that mean that the installation of Phoenix OS erase all the data in that partition?
Regards.
Click to expand...
Click to collapse
I'm not sure about that, only used it on a freshly formatted partition. Mentioned this just to make sure not to be blamed if it should do so.
There's a few things off with these instructions:
1. PhoenixOS does not use a RemixOS folder
2. PhoenixOS's grub.cfg won't boot any RemixOS version especially x64 - as PhoenixOS is 32bit only.
stock phoenixos grub.cfg
Code:
menuentry 'Phoenix OS' --class android-x86 {
search --set=root --file /efi/PhoenixOS/kernel
linux /efi/PhoenixOS/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/PhoenixOS vga=788
initrd /efi/PhoenixOS/initrd.img
}
Something else is going on here. Perhaps the phoenixOS's grub.efi is being used; but it's using the RemixOS grub.cfg. But I think it's just the RemixOS .efi/.cfg and something just switched the default bootloader to grub2 from WBM
HypoTurtle said:
There's a few things off with these instructions:
1. PhoenixOS does not use a RemixOS folder
2. PhoenixOS's grub.cfg won't boot any RemixOS version especially x64 - as PhoenixOS is 32bit only.
stock phoenixos grub.cfg
Something else is going on here. Perhaps the phoenixOS's grub.efi is being used; but it's using the RemixOS grub.cfg. But I think it's just the RemixOS .efi/.cfg and something just switched the default bootloader to grub2 from WBM
Click to expand...
Click to collapse
Maybe, my deeper technical know-how about that is very limited, but I know that it works for me - reproducible. This is just for those like me who tried literally every guide on the net and still none worked. This one probably will. Myself, I find that kind of strange, too and I'm not able to explain why, but it does work. It's just a try and error thing, but for me it works - as already mentioned: reproducible. Got an i7 2nd gen and a X79 Gigabyte Mainboard.
Zwulf said:
Maybe, my deeper technical know-how about that is very limited, but I know that it works for me - reproducible. This is just for those like me who tried literally every guide on the net and still none worked. This one probably will. Myself, I find that kind of strange, too and I'm not able to explain why, but it does work. It's just a try and error thing, but for me it works - as already mentioned: reproducible. Got an i7 2nd gen and a X79 Gigabyte Mainboard.
Click to expand...
Click to collapse
I'm not saying it doesn't work; but what appears to be happening is that the first 'failed' RemixOS installation added things [to efi/esp partition]. And the PhoenixOS install added or replaced something that made the first install work correctly - it could be either the PhOS grub.efi [although that's 32bit] or as simple as it changing your default bootloader.
Download EasyUEFI if you can and see what's in the first partition - I'm just personally curious as to what is going on here.
I'm also using a non-Jide released grub [like Ubuntu users would be - but with a different setup]
HypoTurtle said:
I'm not saying it doesn't work; but what appears to be happening is that the first 'failed' RemixOS installation added things [to efi/esp partition]. And the PhoenixOS install added or replaced something that made the first install work correctly - it could be either the PhOS grub.efi [although that's 32bit] or as simple as it changing your default bootloader.
Download EasyUEFI if you can and see what's in the first partition - I'm just personally curious as to what is going on here.
I'm also using a non-Jide released grub [like Ubuntu users would be - but with a different setup]
Click to expand...
Click to collapse
Sounds very possible... Got EasyUEFI installed but I'm at work atm. Will tell/show you what's in there later this evening when I'm home. The strangest thing I didn't get: original RemixOS booted fine after copying RemixOS folder content to root - but only guest mode worked, not resident. But I mentioned that already in OP. The whole thing would have been a lot easier if I didn't ditch my Arch Linux for RemixOS (for GRUB's sake... ;D), but there were less things to learn...
These instructions didn't work for me, except for the fact that I didn't create a partition. Phoenix would come up as a boot choice but would boot loop.
Sent from my Nexus 6P using Tapatalk
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Vioner said:
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Click to expand...
Click to collapse
I finally managed to find out what I was doing wrong; I assumed a device listed in /storage was my EFI partition, but it turns out it was probably just the EFI folder from RemixOS original installation. I managed to find my EFI on /dev/block/sda1 and editing grub.cfg was spot on.
Thanks for the help, buddy!
GryphonBR said:
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
Click to expand...
Click to collapse
How is Remix running on your switch 12; does everything work properly?
Ludespeed said:
How is Remix running on your switch 12; does everything work properly?
Click to expand...
Click to collapse
Yep, every little thing. The one gripe I've had is when I connect the charger with the computer on standby from Remix OS - not sure what is causing it, but it will reset and I have to do a cold start to get it back to work. But if I take the time to wake it up, connect the charger and then put it back to sleep, no problems.
But other than that, everything is great - sound, WiFi, every port... Oh, one more annoyance - the physical volume keys don't work out of the box. I might be able to get them to, but for now I don't care much about it. And one thing I haven't tried at all is the internal gyroscope, to see if the screen rotates automatically.
Hello,
I'm having an odd issue with Remix OS for PC, and wanted to see if anyone else experienced this and hopefully found a resolution. Please see the bottom of the thread for info on my PC setup. My laptop is definitely more than powerful enough to handle remix, and it used to run fine, but now I seem to have the following issues after not booting into Remix for a while:
***Wifi does not automatically connect, it only connects if I click the wifi icon in the tray (then it connects to my network automatically)
***Nearly all apps will not open, including the Settings app. I'll click on an icon on the desktop, and the icon lights up, registering my click, but the app never opens and the icon stays lit as if something froze. However, I can still "swipe" from the left desktop to the right one, and vice versa.
***When attempting to install an app (Eventually, without any rhyme or reason that I've noticed, I can open the Play Store and maybe the settings app), the app hangs on Installing after it downloads. I've tried waiting a good 20 minutes, but I know the apps install much quicker on this laptop, and I've tried this with small apps.
***Similarly to the above, clicking the Remix OS menu button does nothing as well.
With those symptoms in mind, it seems like there's something holding the system back, but the actual GUI performance is fine. For example, there's no lag or hesitation when an app finally eventually opens or when I click around through the Settings app (when it finally opens). It doesn't seem to only be with graphic intensive apps either, as I tried a simple text/memo app and when that one eventually opens, the desktop background is black and the app window is black with only a menu near the top.
My attempts to fix it
So far, I've tried running an e2fsck -f data.img command to repair the data.img file. It didn't appear to report any issues and the problem did not go away. I've rebooted the thing about a billion times, no luck! Getting into the Settings app is hit or miss and I haven't really had any idea of what setting might help, and installing third party apps appears to not be an option either.
The only other option I could think of would be to backup my data.img and reinstall the OS, and then restore the data.img file, but this seems like it will restore the problem with it. Also, I haven't experienced any problems in Windows, so I don't think there is any issue with the drive. Sorry for such a long thread, just wanted to be detailed!
Any ideas are much appreciated!
My PC: Lenovo Ideapad y510p
Windows OS: Windows 10 64-Bit
Remix OS for PC: 3.0.207 dual booted with the above Windows 10 installation
Hard Drive: 500GB SSD drive
RAM: 16GB
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
ViolentNeurosis said:
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
Click to expand...
Click to collapse
Thank you for the response! In reading the issue you're having, I'm wondering Remix OS for PC, in its current state, is more susceptible to corruption issues in under some circumstances rather than others. When I first installed it, I installed the 64-bit version and I kept having issues where I'd boot it up and it suddenly would not start. I found somewhere on a forum where someone recommended to just use the 32-bit version and the issue went away for a long time, until I had the issue described in my original post. I'm wondering if it just isn't stable enough yet to be run from a flash drive, as it seems to me like it has issues with being easily corrupted.
This brings me to my next comment, I was able to fix my issue! I tried a couple things that didn't work, reinstalling Remix and then choosing YES to erase the entire virtual drive, then copying a backup of my original data.img back into the directory so I don't have to reinstall everything. This didn't fix the issue, so instead I downloaded the 64-bit version and installed it, but this time I chose NO on the prompt to erase my data.
Upon booting into Remix, it gave the standard Android message about optimizing apps and is now running good. I wish I did this workflow with the 32-bit version, as I'm wondering if it would have worked. I suspect I'll experience the same issues I originally experienced with the 64-bit version.
Anyway, I hope this may shed any light on how you can try to resolve your issue. Good luck!