Jump to content











Photo

Windows 8.1 (UEFI Boot) Issues


  • Please log in to reply
248 replies to this topic

#226 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 15 September 2014 - 11:44 AM

Oh, really? Thanks for letting me know. I'll check it out.



#227 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 15 September 2014 - 12:10 PM

That seems to have worked. It said "op success" with the enable flag. Then when I requested info, it said "enabled" and printed out "\\?\globalroot\device\harddisk0\partition1\recovery\windowsre" as the path. However, when I attempted to initiate system recovery, it did not work out; predictably so. I'd actually like to be able to register the last WIM file created by DoubleSpace as the recovery image to use. But I don't know if MS can play ball with that, since in my case the WIM file is located on the same partition as the target partition, where MS seems to segregate the two.



#228 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 15 September 2014 - 12:15 PM

Then when I requested info, it said "enabled" and printed out "\\?\globalroot\device\harddisk0\partition1\recovery\windowsre" as the path. However, when I attempted to initiate system recovery, it did not work out; predictably so. 

 

Maybe I missed something : why is it predictable/obvious? If the WIM actually exists and is enabled, then why would it not work out?



#229 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 15 September 2014 - 12:26 PM

'cause there's a difference between a 250 MB WIM that houses just WinRE and a 5 GB WIM that houses the entire Windows OS.



#230 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 15 September 2014 - 01:19 PM

Either I am confused or you are :

I am talking of using this as a way of injecting ZipMagic into WinRE and then running DoubleSpace.... Which was your objective as I understand it.

 

In no way is WinRE similar to the backing WIM for the WIMBoot volume... For that I think you would use the second property of reagentc, "recovery image", by using /setosimage switch.



#231 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 15 September 2014 - 02:19 PM

Oh, I thought you were talking about this as a way to enable system recovery.

 

I do find it unreliable to parse the output of command line tools, this has been my experience as a software developer.

 

I'm still waiting to hear from that user where DoubleSpace was unable to locate WinRE. I'm pretty sure the latest version of the tool works around that problem, and even this reagent may be using a similar algorithm to mine for locating WinRE :)



#232 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 15 September 2014 - 02:29 PM

May not be as sophisticated as yours :

Enable any custom Windows RE specified by using the [/size]/setreimage option. If no recovery image is specified, the computer attempts to enable Windows RE by using the default Winre.wim from \Windows\System32\Recovery[/size]

 

:)

 

But eventually, when the PC is not booting alright, WinRE is only going to work if it's registered in REagentC. And it can only reset/repair if the recovery Image is registered with REagentC. So you might as well enable them.



#233 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 15 September 2014 - 02:48 PM

Nice to hear :)

 

I doubt any of that is DoubleSpace's business. I don't believe WIMBoot'ing a drive with DoubleSpace would cause any changes to the reagent registration. And if one was previously corrupt on the system, then again, I'm not sure its my business to go around repairing that :D



#234 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 16 November 2014 - 01:39 PM

I am looking for a good imaging backup and restore program, and came upon a puzzling issue :

All the restore tools of the major imaging products use a WinPE-based boot disc to run... But WHY aren't they just injecting them into the WinRE image like you are doing in ZipMagic? That would make for a VERY superior user experience, except for the case where the system drive is also being reimaged.

Is this injection that you have done so innovative that no one else has thought of it yet?

#235 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 12:39 AM

I am looking for a good imaging backup and restore program, and came upon a puzzling issue :

All the restore tools of the major imaging products use a WinPE-based boot disc to run... But WHY aren't they just injecting them into the WinRE image like you are doing in ZipMagic? That would make for a VERY superior user experience, except for the case where the system drive is also being reimaged.

Is this injection that you have done so innovative that no one else has thought of it yet?

 

I think it is. Ironically, I have jaclaz to thank for that!

Someone should probably patent the idea and get ready to troll companies like Acronis as soon as they have woken up to it :)

Maybe all of us at reboot.pro who worked on this project could file jointly for the patent as co-authors.

That would be nice, wouldn't it? Ah, imagine the extent of back-stabbing if the patent actually starts bringing in money!!!

Seriously, it could be an interesting effort. I'm up for it if other people are (provided ZIPmagic gets a free pass, of course).

Anyhow, back to work: Here's calling out to jaclaz, milindsmart, Misty, Synchronicity, Erwan, I've got a new issue:

Currently the boot process is failing on my trusty Surface Pro. It gets to the "Please wait" stage, after having selected the new entry created by DoubleSpace.

At this stage it hangs for probably 5-10 minutes; and then the PC BSODs and resets when I press any key on the keyboard. The BSOD is of the sad smiley type ":(" and no extra information is shown (like the type of failure). I have not had this reported in the field yet, but I am concerned if I am running into it, others might eventually too (to say nothing of being unable to DoubleSpace  my Surface Pro).

How would we go by diagnosing and fixing this issue?

 

I am about to release ZIPmagic 12.78 with significant updates to DoubleSpace (folder exclusions, built-in one-click decompression) and I'd hope to ship the latest update with the solution to this latest problem at hand.


  • TheHive likes this

#236 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 06 March 2015 - 08:24 AM

Patenting sounds wicked! :D I have no idea whether it will be useful and economical, even to extort? :D

 

Regarding the BSOD, there is fortunately a way to get something like the old one back, but there is no mention of Windows 8.1 here it should work with windows 8.1 too : Got to install this hotfix, and add a key at : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

 

I have not tried it out, but I'm going to soon. I hate the smiley bugcheck.



#237 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 09:29 AM

Well its a very legitimate and useful technology...and unlike trolls, it was developed to solve a real need, one that ZIPmagic DoubleSpace had, but a need that would be shared by many other tools undoubtedly!

 

I think with a good sales team behind it, it could be licensed very reasonably to companies like Acronis. In addition to disk imaging companies, any AV company would also benefit - in fact, it might be a blessing for them, since they would be able to scan and repair a possibly infected system offline! Those are just my two quick ideas, I'm sure there's bound to be plenty more.

 

Thanks for the links, will check those now shortly.



#238 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 10:25 AM

UNMOUNTABLE_BOOT_VOLUME

 

I restarted the PC about 4/5 times using the 'abomination' UI (charms | settings | change pc settings | update and recovery | recovery | advanced startup | choosing the options for command prompt), and as I suspected, the PC was unable to boot into the command line either.

 

This is good for DoubleSpace - it shows that nothing has become corrupted in its bowels where things are involved with respect to our new patent-pending media-less full-access instant-reboot technology. However, it does speak badly of my trusty Surface Pro; namely that it has gotten corrupt again somehow.

 

I guess what this means at the end of the day is that my recovery environment has indeed gotten corrupted?

 

How would one go by fixing that, then?



#239 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 10:31 AM

C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition1\Recove
ry\WindowsRE
    Boot Configuration Data (BCD) identifier: 640afa1d-4033-11e4-a666-c8d7196638
c4
    Recovery image location:
    Recovery image index:      1
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.



#240 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 12:49 PM

Nasty problem here. I even replaced the WinRE.wim file with another backup copy from a long past Surface Image.

 

No effect, still failing to boot with same error message.

 

Any way to diagnose further?



#241 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 06 March 2015 - 01:33 PM

Hmm that sounds bad... 

 

Can you explain what you meant by the following? How is it not related to the DoubleSpace algo?

 

This is good for DoubleSpace - it shows that nothing has become corrupted in its bowels where things are involved with respect to our new patent-pending media-less full-access instant-reboot technology. However, it does speak badly of my trusty Surface Pro; namely that it has gotten corrupt again somehow.

 

Just to clarify, what exactly has become unmountable? the winRE.wim volume? the system volume? the main windows volume? things are getting confusing.



#242 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 06 March 2015 - 01:36 PM

The main volume boots.

 

Windows RE does not seem to boot, either when used as a booting template by DoubleSpace, or when used to try and access the command line for Windows recovery, for example.

 

Does that help?



#243 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 09 March 2015 - 07:14 AM

Hmm, then that leaves only one option .... bootmgfw.efi is messed up.



#244 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 09 March 2015 - 09:16 AM

Where does one find that file?



#245 milindsmart

milindsmart

    Frequent Member

  • Advanced user
  • 201 posts
  • Location:Bangalore
  •  
    India

Posted 09 March 2015 - 10:23 AM

The EFI system partition, at \EFI\Microsoft\Boot (or somewhere else. it's a small partition.)

 

Essentially, I'm saying you should boot it with a install/recovery disc, and run 

bcdboot [...] /f UEFI


#246 simonking

simonking

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Australia

Posted 09 March 2015 - 10:46 AM

 

The EFI system partition, at \EFI\Microsoft\Boot (or somewhere else. it's a small partition.)

 

Essentially, I'm saying you should boot it with a install/recovery disc, and run 

bcdboot [...] /f UEFI

What goes in the magical three dot area? [...]



#247 Tripredacus

Tripredacus

    Frequent Member

  • Expert
  • 234 posts
  • Interests:K-Mart-ian Legend
  •  
    United States

Posted 09 March 2015 - 04:25 PM

Something something broken google :dubbio:

 

Spoiler



#248 ltoiau20

ltoiau20
  • Members
  • 1 posts
  •  
    United States

Posted 21 March 2015 - 08:49 AM

So to start up the Bios normally, you need to disable the Hybrid Hibernation (Fast Startup) from the Power Options:
1. Go to the metro Start menu
2. Search for "power options"
3. Select "Modify the action when closing the lid"
4. Select "Modify the settings which are currently unavailable"
5. Uncheck "Activate Fast Start-up (recommended)"
6. Restart the laptop/PC
7. When you see the logo of your laptop/PC, press Esc.
8. Select "Enter setup"
9. Now you`re in the normal BIOS.
10. Enjoy!
More details in this article or just click this guide from Microsoft:

http://answers.micro...aa-57fa783f0759

 



#249 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 23 March 2015 - 11:24 AM

 

In an effort to illustrate that there are consequences to online censorship, the Windows RE Extractor tool by Simon King/ZIPmagic has been removed permanently from download.



reboot.pro's censorship of his posts without even fair warning has left no other recourse. People need to learn there are consequences to their actions, especially those self-professed ignorant hypocrites who live among us, online and offline!



Any attempts to download this file now redirect to ZIPmagic forums with a note on this issue.



Any existing copies of the tool, when run, also redirect to ZIPmagic forums.

 
Does this mean that the attached (which is a copy of the latest version of the tool downloaded from ZipMagic's site at the time it was freely available[1]) "phones home" ?  :w00t: :ph34r: :unsure:
 
To sum up, since you felt cyberbullied by Wonko the Sane's comments, you flooded the board with posts advertising the zipmagic Commercial tool, without asking - as per board rules - permission to the Admin and Owner of the board, and since he removed these posts that were breaking an established rule of the board, as a retaliation you remove access to a free tool?

Culprits (in your altered perception):

  • Wonko the Sane
  • Nuno Brito

People affected by the effects of this retaliation (in real world):

  • SURELY NOT Wonko the Sane
  • PROBABLY NOT Nuno Brito
  • LIKELY everyone BUT the above two people

Level of effectiveness of the retaliation as punishment for the "bad guys": 0
Collateral damages: 100%
 
 
:duff:
Wonko
 
[1] Please note how the tool was declared FREE at the time of release and does NOT include a Licence preventing it's re-distribution.

Spoiler

Attached Files


  • Tripredacus likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users