Solution
7260 X86 Quirk
Seems that 7260 X86 thinks that it is older than 7201 X86 and one can't update. You can do a clean install tho. In times past, you could hack the cversion.ini file to avoid this but M$ has found another way to keep one from upgrading. Now, if only 7261 wouldn't cause the same problem.
Seems that 7260 X86 thinks that it is older than 7201 X86 and one can't update. You can do a clean install tho. In times past, you could hack the cversion.ini file to avoid this but M$ has found another way to keep one from upgrading. Now, if only 7261 wouldn't cause the same problem.
Master Chief
New Member
- Joined
- Apr 15, 2009
- Messages
- 194
So far the leaked 7260 is only "officially" a 32-bit VHD and a modified ISO (of that VHD) by SoLoR just like he did for 7232. I'm hearing that soon (tomorrow? day after?) 7261 will be leaked (64-bit). It doesn't really matter if it's also a VHD since SoLoR will have an ISO up in a few hours after leaking anyway. 
PcBoyGeorge
Senior Member
- Joined
- May 20, 2009
- Messages
- 430
How is there 7261 if 7260 is the RTM? Also won't rtm require new keys are its not rc branch no more. Cause i hope the rc keys did work since i could use them on it. Since i plan on getting the last build before final rtm which is free and works with rc codes then ill stick with it until it expires
Also most things i have seen are fake 7260.
Also most things i have seen are fake 7260.
gws
New Member
- Joined
- Jun 3, 2009
- Messages
- 60
Here is the info for 7261
6.1.7261.0.win7_rtm.090615-1900 Compiled of the 15th
RTM win7_rtm branch :
6.1.7260.0.win7_rtm.090612-2110
6.1.7261.0.win7_rtm.090615-1900
(June 15-19 to continue to assemble. That's the first candidate for the final assembly of Windows 7)
Final RTM Re-build 7300 (Expected)
gws
6.1.7261.0.win7_rtm.090615-1900 Compiled of the 15th
RTM win7_rtm branch :
6.1.7260.0.win7_rtm.090612-2110
6.1.7261.0.win7_rtm.090615-1900
(June 15-19 to continue to assemble. That's the first candidate for the final assembly of Windows 7)
Final RTM Re-build 7300 (Expected)
gws
Last edited:
busydog
New Member
- Joined
- Feb 11, 2009
- Messages
- 1,056
- Thread Author
- #12
7260 X86 Quirk
Seems that 7260 X86 thinks that it is older than 7201 X86 and one can't update. You can do a clean install tho. In times past, you could hack the cversion.ini file to avoid this but M$ has found another way to keep one from upgrading. Now, if only 7261 wouldn't cause the same problem.
Seems that 7260 X86 thinks that it is older than 7201 X86 and one can't update. You can do a clean install tho. In times past, you could hack the cversion.ini file to avoid this but M$ has found another way to keep one from upgrading. Now, if only 7261 wouldn't cause the same problem.
Master Chief
New Member
- Joined
- Apr 15, 2009
- Messages
- 194
Seems that 7260 X86 thinks that it is older than 7201 X86 and one can't update. You can do a clean install tho. In times past, you could hack the cversion.ini file to avoid this but M$ has found another way to keep one from upgrading. Now, if only 7261 wouldn't cause the same problem.![]()
Again, clean install wins. I keep all my files on my external HDD so all I have to go through after a clean install (which happens at least once a week now...) is reinstalling my programs. 7300 is the build that I'm actually going to "permanently" install.
Similar threads
- Article
- Replies
- 1
- Views
- 934
- Replies
- 1
- Views
- 400
- Article
- Replies
- 2
- Views
- 2K
- Replies
- 0
- Views
- 293
- Article
- Replies
- 0
- Views
- 3K
