Grub error 22


Recommended Posts

I've just reproduced this with an Ubuntu live CD and it allows me to browse to the user home directory, read and copy the files with the ubuntu default permissions...

hmm...well, i didn't work for me! perhaps wubi is set up different on mine...i don't know!

If it doesn't allow you to read the files you could always run the file browser as root, by running the command:

"gksu nautilus"

Alternatively you can use terminal to copy your files by using the "cp" command. Do "man cp" to get more details on how the command works.

ok...thanks!

I cannot give you more details on how to fix your Wubi install than those that are available in the pages that I've referenced to you before. This issue never happened to me, so I wouldn't know how to go about fixing it. Maybe try to fscheck the other image "usr.disk", checking the boot options from grub, reinstalling grub. Just guesses here...

If I were you I would, after recovering my files, uninstall Wubi from Windows and make a fresh Ubuntu install using the Ubuntu CD.

alright...ok, cool! i'm currently working at getting the problem solved on ubuntu forums...hopefully someone can come up with a fix for the crc error...but if they don't, then i will indeed uninstall Wubi, and probably reinstall Ubuntu the conventional way, i.e. on a different partition, so i wont get the same problem again!

Thanks for all ur help! i really appreciate it!!

Cheers! :D

hmm...well, i didn't work for me! perhaps wubi is set up different on mine...i don't know!

No. Wubi has nothing to do with filesystem permission. Anyway, the solution was provided.

Just a quick question, have you by now managed to recover your files...?

alright...ok, cool! i'm currently working at getting the problem solved on ubuntu forums...hopefully someone can come up with a fix for the crc error...but if they don't, then i will indeed uninstall Wubi, and probably reinstall Ubuntu the conventional way, i.e. on a different partition, so i wont get the same problem again!

Thanks for all ur help! i really appreciate it!!

Good luck in doing that. Also may I ask why you would insist in recover instead of a 15min install of Ubuntu with the CD?

No. Wubi has nothing to do with filesystem permission. Anyway, the solution was provided.

Just a quick question, have you by now managed to recover your files...?

not yet, because i haven't yet tried it!!! :no: i've been doing other stuff on my computer, and so have not yet tried it!

Cheers, though! i WILL!

Good luck in doing that. Also may I ask why you would insist in recover instead of a 15min install of Ubuntu with the CD?

ok...two reasons! the first is simply because i have a feeling that this particular problem might happen again, even after a fresh install, and so i would really like to get a solution to the crc error, not just "uninstall and reinstall wubi", which is the kind of answer i've been getting all over...not just here! the second is, it seems lame to me that no one, it appears, has come up with a REAL solution to the problem, despite the fact that its a VERY common issue on wubi...and so i was hoping to prompt people to work on it, and actually SOLVE it, not just tell the users who it happens to: "just reinstall wubi"!!!

I hope this answers ur question, and if it doesn't, looking forward to hearing from u again...

Coolname007

P.S. i'll let u know whether or not the solution for getting my files out of ubuntu and into Windows works!!! Cheers! :D

and so i was hoping to prompt people to work on it, and actually SOLVE it, not just tell the users who it happens to: "just reinstall wubi"!!!

Well then the best solution for that is for you to make a bug report to the Wubi project, not go about asking people on a forum to fix it. There's limits to what those people can do.

P.S. i'll let u know whether or not the solution for getting my files out of ubuntu and into Windows works!!! Cheers! :D

You've already mounted the image, you just need to know how to copy your files. And that is already explained to you in previous posts.

Well then the best solution for that is for you to make a bug report to the Wubi project, not go about asking people on a forum to fix it. There's limits to what those people can do.

good idea!!! i'll probably do that as well!

You've already mounted the image, you just need to know how to copy your files. And that is already explained to you in previous posts.

uhh...lechio??? i wasn't asking a question when i said that...i was making a statement!!! of course i now know (thanks to u!) how to mount the partition, and also to copy files as root user...i was just simply saying that i would try it, and let u know if it worked or not!!!

which i will now proceed to go do now...

ok, lechio...it WORKED!!! now i have successfully backed up my files into Windows, and can discard wubi, if no one comes up with a fix to the crc error!

Thanks for all ur help!!! i have decided that i'm going to post here as well as other places the COMPLETE process of mounting a failed wubi system, using a LiveCD, and recovering ur files! no need for anyone else that has the same problem to have so much difficulty in mounting their OS, and recovering their files!

Cheers! :)

Ok...so here is the COMPLETE process of mounting ur Windows partition, using a Ubuntu Desktop CD (or any other LiveCD!), and recovering ur files:

sudo mkdir /win
sudo mount /dev/sda3 /win

Note: the “sda3” should be replaced (if not correct) with the correct partition that Windows is installed on! It was “sda3” in my case, and would probably be the same for most Vista users, but the person should check first to see if it is the correct partition. In my case, I had to automount the OS by going to Places>OS, and then opening up a terminal, ran “df” which showed me which partition the OS was on. If anyone wants to verify that I know what I’m talking about, here is the Wubi Guide, in which can be found the same basic instructions, only in it they advise u to use “sda1” (which didn’t work for me, as Windows was on sda3). It also doesn’t describe how to recover ur files…which is why I’m typing this right now!

Ok…time to mount the virtual disk!!!

sudo mkdir /vdisk 
sudo mount -o loop/win/ubuntu/disks/root.disk /vdisk

Now the content of the virtual disk can be viewed by simply opening up a file browser (Places>Computer>) and steering to the folder called “vdisk”, after first, of course, opening up the file system! Now simply (once inside of “vdisk”), go to “Home”, and there u will find all ur important documents and files stored neatly inside of there (that is, of course, if when u had ubuntu working ok, u saved ur work in ur Home folder!).

You can also try running a filesystem check (even though it didn’t fix the problem, in my case…who knows! Maybe you’ll have better luck!):

sudo fsck /win/ubuntu/disks/root.disk

For me, all this did was recovered a “journal”, after which it said that the disk was “clean”…but when I tried booting into ubuntu, I still got the same crc error! But u should still try running it, just to wrap up all loose ends, and to make sure that u did all that u could to fix the error!

Oh, and one more thing! Before u can copy ur files from ur ubuntu disk into Windows, or whatever ur main OS is, u will first have to run the following:

gksu nautilus

This command simply opens up the file browser as a root (administrator) user, so u can read and write the files that r therein! An alternative way to to copy files (using the Terminal) is:

cp

This is simply another method of copying!

Hope all this info helps somebody, and helps them to rescue their important files that r in their failed ubuntu! :)

Edited by Coolname007

Hey, thanks for taking the time to type up the process you went through, and hope this helps the next person that runs into the same problem. (Y)

Thanks, also, to Lechio, who had the perseverance to see this to a successful conclusion.

Hey, thanks for taking the time to type up the process you went through, and hope this helps the next person that runs into the same problem. (Y)

Thanks, also, to Lechio, who had the perseverance to see this to a successful conclusion.

no problem!!! :D

i'll second that thanks to Lechio...even though i think i already thanked him! hahaha (i'm sure it wouldn't hurt to thank him again!)

Thanks, lechio!!! :trout:

Edited by Coolname007
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!