(resolved..nuked) 1709 kicking my butt on this one.."We can't tell if your PC has enough space"...

YeOldeStonecat

YeOldeStonecat

Well-Known Member
Reaction score
6,757
Location
Englewood Florida
1709error.png
Stuck on 1607. Had a 100 meg recovery partition from OEM days, of Win7, I delparted it. Now I got this.
My C drive is only using about 80 gigs of that 280 gigs.
diskmangler.png
 
Hmmmm.
Doing a quick google search it looks like most issues relating to this is the "Boot Record"
Maybe have a try in that direction.
 
I have seen issues on a few HPs where the hidden system partition was filled up with some HP junk and, without space on it, Windows couldn't update. Pretty sure that was on Windows 10. Maybe try expanding the hidden partition to 200MB. If I recall, the HP fix involved deleting some unimportant language files that HP put there.

UPDATE: I just saw that all the space was free on that partition. Didn't realize I could embiggen the picture, so I just gleaned over it rather than strain.
 
I've run into this twice before. Once it was fixed by using another install media (first flash drive must have been corrupted). One was fixed as @HFultzjr mentioned... by fixing the boot record. I booted into startup repair and did a bootec /fixmbr followed by a bootrec /fixboot .
 
Krynn72 said:
I've run into this twice before. Once it was fixed by using another install media (first flash drive must have been corrupted). One was fixed as @HFultzjr mentioned... by fixing the boot record. I booted into startup repair and did a bootec /fixmbr followed by a bootrec /fixboot .
Click to expand...
I have never had bootrec work for me. Ever. It's good to know that if I keep trying it, it will work some day.
 
Kirby said:
I have never had bootrec work for me. Ever. It's good to know that if I keep trying it, it will work some day.
Click to expand...
I'm surprised. I mean its obviously only going to help when the problem is being caused by a boot record issue, but I have a pretty good success rate with it when I determine the boot record to be the cause. It was much more common in the Win 7 days.
 
Krynn72 said:
I'm surprised. I mean its obviously only going to help when the problem is being caused by a boot record issue, but I have a pretty good success rate with it when I determine the boot record to be the cause. It was much more common in the Win 7 days.
Click to expand...
I've used it quite a few times when a Google search suggested it. It has never fixed the particular problems I was having. To be fair, I was a lot more capable of learning when I was a younger man and I still haven't gotten all the new Windows tech down in my head yet as to how it all works together.
 
Slaters Kustum Machines said:
I would backup anything important and do a diskpart /clean on the drive then install fresh.
Click to expand...
Sometimes that's easier said than done, though. I have one in here right now where the Pictures folder is 106GB and another folder is 107GB. I haven't even checked the rest of the stuff. And all of it is "must save". Fortunately she gave me a 1TB USB 2.0 external drive to put it on... So, yeah, I'm on day 3 of trying to fix it instead.
 
So...I ran a checkdisk...she stopped at 13% for the longest time. Pulled drive, slaved on bench rig, ran checkdisk from there...went through a ton of stuff. Something whacked that source hard drive....no wonder.

So...too much time spent already, put an SSD in and installing Win10 from the 1709 bootable USB. Hopefully will activate since the host rig was upgraded to Win10 from 7 back about 2 years ago, OEM HP biz workstation.
 
YeOldeStonecat said:
So...I ran a checkdisk...she stopped at 13% for the longest time. Pulled drive, slaved on bench rig, ran checkdisk from there...went through a ton of stuff. Something whacked that source hard drive....no wonder.

So...too much time spent already, put an SSD in and installing Win10 from the 1709 bootable USB. Hopefully will activate since the host rig was upgraded to Win10 from 7 back about 2 years ago, OEM HP biz workstation.
Click to expand...
Shouldn't be a problem. I haven't had to enter a key in my PC since 10 came out in 2015, and probably N&P'd four times since. One also involved an upgrade to a bigger SSD and it didn't complain about it.

Hey, at least you get an SSD out of it.
 
YeOldeStonecat said:
So...I ran a checkdisk...she stopped at 13% for the longest time. Pulled drive, slaved on bench rig, ran checkdisk from there...went through a ton of stuff. Something whacked that source hard drive....no wonder.

So...too much time spent already, put an SSD in and installing Win10 from the 1709 bootable USB. Hopefully will activate since the host rig was upgraded to Win10 from 7 back about 2 years ago, OEM HP biz workstation.
Click to expand...
If it won't activate you still have options. There's still a way to get the free Windows 10 upgrade using some accessibility version or something. I did it once, but I don't remember for sure. BUT, it would mean reinstalling Windows 7 with the actual key, then upgrading that, then nuking and paving THAT for a fresh install of Windows 10 which will activate with that key. Well, I suppose the upgrade install would be good enough, but...well, you know.

But yeah, I'm not really sure how an OEM install upgraded will work since they don't use the actual product key located on the case. Let us know, though. I'd be interested to find out.
 
Kirby said:
If it won't activate you still have options. There's still a way to get the free Windows 10 upgrade using some accessibility version or something. I did it once, but I don't remember for sure. BUT, it would mean reinstalling Windows 7 with the actual key, then upgrading that, then nuking and paving THAT for a fresh install of Windows 10 which will activate with that key. Well, I suppose the upgrade install would be good enough, but...well, you know.

But yeah, I'm not really sure how an OEM install upgraded will work since they don't use the actual product key located on the case. Let us know, though. I'd be interested to find out.
Click to expand...

The Windows 10 Upgrade using "Assistive Technologies" method...they officially pulled that down earlier this month.

It activated fine...first boot it was activated. Detected that this PC had Win10 on it before and phoned home and matched the hash and all was well.
 
YeOldeStonecat said:
The Windows 10 Upgrade using "Assistive Technologies" method...they officially pulled that down earlier this month.

It activated fine...first boot it was activated. Detected that this PC had Win10 on it before and phoned home and matched the hash and all was well.
Click to expand...
Sweet! Good to know that works. Don't really know how I feel about the Assistive Technologies things being pulled, though. I guess, if I had to nail it down to a single feeling, it would probably be "meh". Not a Win10 fan. Of course, I'm even less of a Win8 fan. ESPECIALLY with a laptop touchpad. Stupid little useless things are always popping up from the sides because I touched the touchpad's g-spot or something. Like a regular g-spot, I have only a vague idea where it might be and every time I've hit it, it was an accident.
 
Kirby said:
I have seen issues on a few HPs where the hidden system partition was filled up with some HP junk and, without space on it, Windows couldn't update. Pretty sure that was on Windows 10. Maybe try expanding the hidden partition to 200MB. If I recall, the HP fix involved deleting some unimportant language files that HP put there.

UPDATE: I just saw that all the space was free on that partition. Didn't realize I could embiggen the picture, so I just gleaned over it rather than strain.
Click to expand...

+1 for what may be the first use of "embiggen" on Technibble.
 
  • Like
Reactions: GTP
Kirby said:
Sweet! Good to know that works. Don't really know how I feel about the Assistive Technologies things being pulled, though. I guess, if I had to nail it down to a single feeling, it would probably be "meh". Not a Win10 fan. Of course, I'm even less of a Win8 fan. ESPECIALLY with a laptop touchpad. Stupid little useless things are always popping up from the sides because I touched the touchpad's g-spot or something. Like a regular g-spot, I have only a vague idea where it might be and every time I've hit it, it was an accident.
Click to expand...
The assistive technology method was a pure BS publicity stunt. NO ONE who got Windows 10 via that method couldn't have just gotten it by just running the Windows 10 installer and inputting their valid Windows 7 key. There are no blind or deaf persons who only got Windows 10 via this method. NO ONE. Everybody can still upgrade to Windows 10 without issue.
 
Computer Bloke said:
Oh, that's easily fixed:

Code: 
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell\EdgeUI]
"DisableCharmsHint"=dword:00000001
"DisableTLcorner"=dword:00000001

With that in place you need to move the mouse into the top right corner and then down in order to bring up the Charms Hint, which is much more sensible, and as a bonus it turns off the App Switcher that pops every time you move the mouse pointer to the top left corner (which you'd think was a natural place to park it when you're not using it).
Click to expand...
I got all excited when I read that first sentence there. I thought I was going to get some WAY different advice there.

On a side note, I wasn't talking about moving the mouse into the lower-right corner to bring up the Charms Bar. I'm fine with that. I was talking about the bar coming up when you put your finger down on the mouse pad if it's too close to the right edge it just comes up automatically. Just put your finger down on the mouse pad, start moving left, Charms Bar. To me it makes the mouse pad all but unusable because there's all this "forbidden space" on the right hand side which isn't clearly marked.

mraikes said:
+1 for what may be the first use of "embiggen" on Technibble.
Click to expand...
Unfortunately I think I Trumped it. I'm pretty sure it would be "enbiggen", not "embiggen".
 
Last edited:
[QUOTE="Kirby, post: 628820, member: 12138]

Unfortunately I think I Trumped it. I'm pretty sure it would be "enbiggen", not "embiggen".[/QUOTE]

I think the theory is that embiggen's roots are similar to embolden's.

In the way that someone may be emboldend and become bolder, something may be embiggened and become bigger.
 
Last edited:
You must log in or register to reply here.

Similar threads

T
A good Software List..must see!!
Replies
11
Views
8K
nesrinamb
N
A
My PC Toolkit - VERY LONG LIST
Replies
14
Views
3K
kagman
kagman
Back
Top