u/Wise-Policy-3683

Can AI-enhanced humans discover L[1/4] factoring algorithm?

There are certain rumours in certain corners of the internet that NSA/GCHQ have an L[1/4] factoring algorithm, i.e. they may be able to beat the number field sieve, at least in theory.

Assume for one second this is true, or if not, at least that L[1/4] exists.

Many people say that AI is just a next-word guesser etc, but there is no doubt about its usefulness in presenting relevant material before the eyes of a human.

No-one has publicly discovered L[1/4] factoring despite half a century of intense research. Publicly, humans thus far have failed on their own.

Can AI-assisted research conceivably push the boundaries just a bit beyond the collective genius of human mathematicians, through e.g. time saving in experimentation/scripting, connection of ideas, judicious human postulation with dead ends abandoned and promising avenues explored more quickly than ever before, and find that L[1/4]?

reddit.com
u/Wise-Policy-3683 — 1 day ago

Recent Windows 10 -> 11 in-place upgrade, state repository service at 17% cpu, FIXED

I recently upgraded from Windows 10 to Windows 11. Since then, I noticed the cpu fans coming on much faster than usual. I check Task Manager, cpu at above 17% with one service in particular - "State Repository Service", and no clue what the real issue is.

This is now resolved (for me), posting this to help others - however - be careful with these commands, if you get impatient and quit out of them it might make it worse. It can take a couple of hours. The worst case is you might need to reinstall. /End disclaimer

I think the problem was the in-place upgrade didn't set some things up in the optimal way. Actual Microsoft programmers might of course know the technical reason. The solution was to run some powershell commands (as administrator) and wait for them to finish, then reboot.

Here goes:

Note: This is not instant. It can take 30-60 minutes total, and you MUST let the commands finish even if they look stuck.

  1. Open Task Manager (Ctrl+Shift+Esc).

  2. Click File > Run new task. Type 'powershell', check the Admin box, and hit OK.

  3. Run these three commands one by one:

```DISM /Online /Cleanup-Image /RestoreHealth```

(This fixes the Windows 'master files'. It often hangs at 20% for a long time. Wait for it to hit 100%.)

```sfc /scannow```

(This replaces your broken files with the fixed ones. Takes about 10-15 minutes.)

```Get-AppxPackage Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}```

(This re-installs the actual Start Menu. It might show red error text—ignore it and wait for the blinking cursor to return.)

  1. Reboot your computer.

Summary: The high CPU happens because your Start Menu is "stuck" in a crash loop. These commands force Windows to download healthy files and re-link the menu properly. If you don't wait for the progress bars to finish, it won't work.

Happy Windows-ing all.

reddit.com
u/Wise-Policy-3683 — 2 months ago