Windows 10 Recovery drive

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that important.

Thanks for any pointers.

Rene

On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.

--
Peter Kozlov

On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it just
now and still no luck, Will pick up a 64 GB next time I'm uptown and
try again later.

Rene

On 05/25/2018 11:13 AM, Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it just
now and still no luck, Will pick up a 64 GBÂ* next time I'm uptown and
try again later.

Rene

I just did mine last night on a 32 gig drive and it worked fine.
Didn't on a 16G.
But I'm sure a 64 won't hurt the pocket book too much.

On Fri, 25 May 2018 13:35:10 -0400, Big Al wrote:

On 05/25/2018 11:13 AM, Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it just
now and still no luck, Will pick up a 64 GB* next time I'm uptown and
try again later.

Rene

I just did mine last night on a 32 gig drive and it worked fine.
Didn't on a 16G.
But I'm sure a 64 won't hurt the pocket book too much.

I just bought a few extra 64 GB SanDisk thumb drives for about $16
each. They're so cheap now. Won't even bother going smaller than this.

--
Peter Kozlov

Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it just
now and still no luck, Will pick up a 64 GB next time I'm uptown and
try again later.

Rene


I'm running one off in Virtualbox right now.

The process is pretty slow.

You can add a "USB controller" to the Storage section
in VirtualBox and use a VHD file as a USB stick.

Paul

On 05/26/2018 1:35 AM, Paul wrote:
Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it
just now and still no luck, Will pick up a 64 GBÂ* next time I'm uptown
and try again later.

Rene


I'm running one off in Virtualbox right now.

The process is pretty slow.

You can add a "USB controller" to the Storage section
in VirtualBox and use a VHD file as a USB stick.

Â*Â* Paul


Today I recieved a new Sandisk Ultraflair 64GB USB 3.0 drive and again
tried to do the Windows 10 recovery drive with files checked, Again with
no success.
So it's not the size that counts in this case.
So I give up on this not too important experiment.

Rene

Rene Lamontagne wrote:
On 05/26/2018 1:35 AM, Paul wrote:
Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it
just now and still no luck, Will pick up a 64 GB next time I'm
uptown and try again later.

Rene


I'm running one off in Virtualbox right now.

The process is pretty slow.

You can add a "USB controller" to the Storage section
in VirtualBox and use a VHD file as a USB stick.

Paul


Today I recieved a new Sandisk Ultraflair 64GB USB 3.0 drive and again
tried to do the Windows 10 recovery drive with files checked, Again with
no success.
So it's not the size that counts in this case.
So I give up on this not too important experiment.

Rene

Is this a "reagentc" problem like when you tried to do
this quite a while ago ?

My output was only 4GB or so, which seems like just
enough to reinstall the system. And I didn't see
a Program Files folder either, which worried me a bit.

The stick should have two WIM files. A 300MB WIM to
boot the USB stick, and a 3.5GB WIM with the system
files. The 300MB WIM could be one based on reagentc
files or similar.

The slow progress is caused by the file compressor,
which applies "7Z quality" compression to the 3.5GB WIM.
It should really use more cores while it's doing that
compression (use the whole machine).

Paul

On 05/29/2018 2:51 PM, Paul wrote:
Rene Lamontagne wrote:
On 05/26/2018 1:35 AM, Paul wrote:
Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I
get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other
versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it
just now and still no luck, Will pick up a 64 GBÂ* next time I'm
uptown and try again later.

Rene


I'm running one off in Virtualbox right now.

The process is pretty slow.

You can add a "USB controller" to the Storage section
in VirtualBox and use a VHD file as a USB stick.

Â*Â*Â* Paul


Today I recieved a new Sandisk Ultraflair 64GB USB 3.0 drive and again
tried to do the Windows 10 recovery drive with files checked, Again
with no success.
So it's not the size that counts in this case.
So I give up on this not too important experiment.

Rene

Is this a "reagentc" problem like when you tried to do
this quite a while ago ?

My output was only 4GB or so, which seems like just
enough to reinstall the system. And I didn't see
a Program Files folder either, which worried me a bit.

The stick should have two WIM files. A 300MB WIM to
boot the USB stick, and a 3.5GB WIM with the system
files. The 300MB WIM could be one based on reagentc
files or similar.

The slow progress is caused by the file compressor,
which applies "7Z quality" compression to the 3.5GB WIM.
It should really use more cores while it's doing that
compression (use the whole machine).

Â*Â* Paul


I can't tell, it doesn't write anything to the drive or even acknowledge
any drive , Same as before with past tries. the green bar floats across
5 or 6 times then the message appears, Seems more like a hardware issue
than software, as it does the same thing on many Windows versions, so
I'm thinking its not a Windows fault as it works for others.

Rene

On Tue, 29 May 2018 15:23:58 -0500, Rene Lamontagne
wrote:

On 05/29/2018 2:51 PM, Paul wrote:
Rene Lamontagne wrote:
On 05/26/2018 1:35 AM, Paul wrote:
Rene Lamontagne wrote:
On 05/25/2018 10:02 AM, Peter Kozlov wrote:
On Fri, 25 May 2018 09:50:07 -0500, Rene Lamontagne
wrote:

Why can I not make a Recovery drive on this PC?

I can do one if I uncheck system files but not if it is checked, I
get
the Cannot create error no matter what.

Am running 17134.48, on an i7 950 CPU on an Asus X58 Sabertooth
motherboard 6GB of memory, also have tried this on many other
versions
before this and was unsuccessful.

I have done sfc/scannow with no bad results, I have tried 4 or 5 USB
sticks from 8 to 32 GB with no luck.

Any other Ideas to try? or should I just forget it, Its not that
important.

Thanks for any pointers.

Rene


Strange. I just started thinking about the whole recovery thing about
a week ago. Mine does indeed let me make a recovery drive with the
system files checked. What I would try is inserting a larger thumb
drive into your USB slot before you run that utility and see if that
resolves your problem. Typically it asks for 16 GBs but I have made
one just recently that took about 35 GBs and I used a 64 GB thumb
drive. Give that a try and report back.


Thanks Peter, The biggest I have on hand is a 32 GB stick, Tried it
just now and still no luck, Will pick up a 64 GB* next time I'm
uptown and try again later.

Rene


I'm running one off in Virtualbox right now.

The process is pretty slow.

You can add a "USB controller" to the Storage section
in VirtualBox and use a VHD file as a USB stick.

*** Paul


Today I recieved a new Sandisk Ultraflair 64GB USB 3.0 drive and again
tried to do the Windows 10 recovery drive with files checked, Again
with no success.
So it's not the size that counts in this case.
So I give up on this not too important experiment.

Rene

Is this a "reagentc" problem like when you tried to do
this quite a while ago ?

My output was only 4GB or so, which seems like just
enough to reinstall the system. And I didn't see
a Program Files folder either, which worried me a bit.

The stick should have two WIM files. A 300MB WIM to
boot the USB stick, and a 3.5GB WIM with the system
files. The 300MB WIM could be one based on reagentc
files or similar.

The slow progress is caused by the file compressor,
which applies "7Z quality" compression to the 3.5GB WIM.
It should really use more cores while it's doing that
compression (use the whole machine).

** Paul


I can't tell, it doesn't write anything to the drive or even acknowledge
any drive , Same as before with past tries. the green bar floats across
5 or 6 times then the message appears, Seems more like a hardware issue
than software, as it does the same thing on many Windows versions, so
I'm thinking its not a Windows fault as it works for others.

Rene


Sorry about that. Thought for sure that size would have solved it for
you. Mine took 35 GBs in the most recent one I made. That whole 16 GB
thing needs to be updated I think.

--
Peter Kozlov

Rene Lamontagne wrote:

I can't tell, it doesn't write anything to the drive or even acknowledge
any drive , Same as before with past tries. the green bar floats across
5 or 6 times then the message appears, Seems more like a hardware issue
than software, as it does the same thing on many Windows versions, so
I'm thinking its not a Windows fault as it works for others.

Rene

Did the stick have initial formatting ?
Did you quick format the stick as NTFS or FAT32 ?

It will reformat the stick anyway, but may go
off in a huff if you offer a brand new storage
device where the MBR hasn't been initialized yet.

*******

In an Administrator Command Prompt, you can try

reagentc /info

and see if the field definitions look reasonable.

Mine and some other peoples 17034 update, causes
the appearance of a couple 500MB or so partitions,
and one side effect appears to be a working,
properly initialized reagentc setup. Unlike
the last time... One of the two ~500MB partitions
contains the working reagentc WIM.

Paul

On 05/29/2018 3:53 PM, Paul wrote:
Rene Lamontagne wrote:

I can't tell, it doesn't write anything to the drive or even
acknowledge any drive , Same as before with past tries. the green bar
floats across 5 or 6 times then the message appears, Seems more like a
hardware issue than software, as it does the same thing on many
Windows versions, so I'm thinking its not a Windows fault as it works
for others.

Rene

Did the stick have initial formatting ?
Did you quick format the stick as NTFS or FAT32 ?

It will reformat the stick anyway, but may go
off in a huff if you offer a brand new storage
device where the MBR hasn't been initialized yet.

*******

In an Administrator Command Prompt, you can try

Â*Â* reagentc /info

and see if the field definitions look reasonable.

Mine and some other peoples 17034 update, causes
the appearance of a couple 500MB or so partitions,
and one side effect appears to be a working,
properly initialized reagentc setup. Unlike
the last time... One of the two ~500MB partitions
contains the working reagentc WIM.

Â*Â* Paul

Don't know much about reagentc but it says enabled and operation successful.
The stick is formatted Fat32 and has a few Sandisk files on it from the
factory.

Rene

Rene Lamontagne wrote:
On 05/29/2018 3:53 PM, Paul wrote:
Rene Lamontagne wrote:

I can't tell, it doesn't write anything to the drive or even
acknowledge any drive , Same as before with past tries. the green bar
floats across 5 or 6 times then the message appears, Seems more like
a hardware issue than software, as it does the same thing on many
Windows versions, so I'm thinking its not a Windows fault as it works
for others.

Rene

Did the stick have initial formatting ?
Did you quick format the stick as NTFS or FAT32 ?

It will reformat the stick anyway, but may go
off in a huff if you offer a brand new storage
device where the MBR hasn't been initialized yet.

*******

In an Administrator Command Prompt, you can try

reagentc /info

and see if the field definitions look reasonable.

Mine and some other peoples 17034 update, causes
the appearance of a couple 500MB or so partitions,
and one side effect appears to be a working,
properly initialized reagentc setup. Unlike
the last time... One of the two ~500MB partitions
contains the working reagentc WIM.

Paul

Don't know much about reagentc but it says enabled and operation
successful.
The stick is formatted Fat32 and has a few Sandisk files on it from the
factory.

Rene

Then it should have appeared as an output option
(in case more than one USB stick is present, they
have to give the option to select one of your
USB sticks).

https://www.howtogeek.com/131907/how...-in-windows-8/

Paul